All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
In Collect, you are restricted from registering any Webapp database as a source in Collect. While I understand and agree with the intent here, I don't think it should apply to DataConstructionServer. The entire point of DCS is to collect source data that does not exist. Our methodology is such that in order to reference the data you should move the data to a static copy in sdbDCS before using it in downstream processing. It can then be on the same refresh schedule as all other sources and not impacted by users changing data while in process.
The current workaround recommended by support is to create an additional DataSource with a different name but pointing to the same database. This works from a technical perspective but is not as clean or clear as to what is happening. It is also not obvious that you would need to do this and I imagine will need to many future support tickets.
Guest
