If a user clicks an action button, I want to lockdown the data in table that's available to that user so that he cannot change or modify it later. Once done, it should be frozen! Any approach to achieve this functionality is highly appreciated.
@mohitlamba0101
You can achieve the functionality by using a simple concept of Dynamic Cell access. Follow the below steps
Step 1) Create a DCA module with three line items, two boolean formatted and one 'No Data' formatted. Dimension the module by user list.
Step 2)
Use the above module as a read/write access driver for the data module, where you want to lock the data for user entry.
Step 3)
Create an action which will copy the 'No Data' field into 'Write' line item of your DCA module. This will act as the action to 'Lock' the data module.
After entering the desired input the user have to run this action to lock the fields. To unlock, simply check the 'Write' boolean.
I hope it helps
~Anand
Hi Anand,
I tried this but can you please elaborate the third step because no action is generated to create the button when I perform the instructions.
When you import the 'Lock' line item into the 'Write' line item, an import action will be created for sure. You can publish that particular action on the dashboard. To elaborate
Step 1) Create a saved view keeping only the 'Lock' line item field.
Step 2) Now import it into the main view of the module by mapping the Write line item to the Lock line item.
An import action gets created in the Imports section of the Actions.
Let me know if things are still not clear.
I need to flow data from a model DAT01a in PBF Dev to PBF Consol, we use connectors to do this OUT3A and OUT3B Any instructions or tips on how to build or test the data can be flowed through to PBF Consol?
Hi, My values of monthly commission forecast is not matching the Check your build values. Please help to identify where I am wrong. As I have attached screenshots of the blueprint and module grid view. Thanks, Sre Varshaa S
In our current setup on a Global Engagement, most regions use a Month–Year format (e.g., Jan-26) for the time range in the forecast upload template. However, the US region follows a Year–Month format (e.g., 26-Jan) in their local Excel files. This mismatch creates a challenge: When US users download the template, it is…
