Is it possible to place a restriction on a scenario member to prevent data write via XFSet? This would prevent data load via XFSet for Actuals (so the workflow can't be bypassed), however would allow data send via XFSet for budget / forecast scenarios. Would appreciate any input if other users have dealt with this issue in the past.
Hi SW01,
In case only Import data applies to the Actual scenario, maybe you can enforce that by not having any Forms profile type enabled for the Actual scenario type?
By not having a Forms step enabled on the WFs where the entities are assigned, no Forms data will be accepted (being via Cube Views or XFSet).
Expanding this question to QuickViews and the ability to submit data from excel. In our example we have Import, Form (Cash Flow Walk,...) and ADJ (Journals) channels in all our Actual WF's. No Forms allow updates that impact Financial information and JE already have control on them. We do have some advanced Excel users that could create QuickViews and submit data directly to Actuals. Is there a way to prevent this. To us this is an Audit Issue that we feel our Auditors are going to get on us about.
