FAQs on Writeback

a. In Lumel EPM, a user makes a change to a data input column in read mode and closes the item. Would they be able to see the latest data the next time they reopen it?

Yes, they would be able to. Lumel EPM captures adjustments to data input columns and saves them in its backend application DB. This works regardless of whether the item is in read or edit mode. If a user makes any changes to data input columns (provided they have permissions to do so in read mode), Lumel EPM stores the latest value in its backend database. Upon reopening, the latest data input column values are fetched from the backend DB, and the table is loaded with the latest data.

b. What happens to RLS for users using Lumel EPM?

Lumel EPM respects the RLS applied in the original dataset. It displays only rows that a user is supposed to view. Please note RLS works only for users with "Viewer" access in the Fabric workspace.

c. What happens to writeback for users with RLS?

Lumel EPM will only writeback rows that apply to the user performing the writeback. If a user only sees 3 dimension categories (as per RLS even though there are 10 total dimension categories in the dataset), they can only writeback rows related to 3 dimension categories. This is because they would only be able to see 3 dimensions. In simpler terms, you only writeback what you see on the display.

d. How would the data be stored if multiple users are performing writeback? When does Lumel EPM overwrite rows or append rows?

Lumel EPM performs writeback operations sequentially. For each operation, Lumel EPM compares new writeback rows to existing DB rows and will overwrite only if all the dimension column names and values match. However, if you would prefer Lumel EPM not to overwrite rows during writeback commits, select Writeback only changes/Delta writeback as the writeback type. Under this mode, Lumel EPM retains previous values.