Hello.
I want to know if it's possible to block/restrict the creation of an item ( via a FORM ) based on a line item. For example, if the total wallet = 0 then the user should not be able to add and create a new item. thank you
@SofianeLz
You will need to create a boolean formatted line item with your logic in it. If the logic is true, it will allow a button to be pushed, if it is false, the button is not clickable. I have written the logic in your example as "Total Wallet <> 0".
From there, in the action card configuration, create your form. once that is done, click on "Manage", then the 3 dots for more options on the form you just created, then "Select Driver Line Item"
Finally, Select your Module, your driver line item, and then click "Create". You can now publish your page. If my "total wallet" is 0 then the button is greyed out.
If any other value is in my total wallet, then the button is clickable:
Hope this helps! Jason
Hey, we have the DCA at action level, but I am curious to ask at what level you have this Total Wallet line item? Can it be taken in a module and line item with no dimension like Jason did in his explanation?
Hi you can use select driver line-item option while configuring the card.
@PujithaB @Dikshant @jasonblinn thank you all for the answers. The select driver line item is the perfect solution. Have a great day y'all
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context andβ¦
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-yearβ¦
