Account Lock - Allow Input false
HI
Am looking to lock the accounts (Rev first and then COGS ), such that if the Rev load is done i should be locking the Rev account for a particular scenario, then lock COGS account based on the I...
Forum Discussion
Hi, yes, that is correct, the WF steps need to be split up. If they are not split up, the import would fail even without WF channels if one theoretically locks the Rev accounts a different way, assuming the users re-load the same dataset (but with updated COGS numbers), because they would try to load to (b)locked accounts. This is why the system requires this split either way.
If you are concerned about a direct connection that loads all data, this can be split as well and only pull the relevant data for the relevant accounts. If the users only have a single source file they manually load, the different steps can use different transformation rules, bypassing the accounts that are not supposed to be loaded in the respective WF step (e.g. bypass Rev accounts in the COGS load step).
The Allow Input property on an account is neither time nor scenario dependent. So even if you were to use this property, you'd be blocking this for everything. And for the next load one would need to re-open the members.
