In the screenshot below, my client is sending sales quotes through their CRM in Noloco. When a Sales Quote has been sent, it’s status is automatically marked as “Sent” which should (1) restrict new line items from being added (which can be accomplished by configuring the default New Record collection button’s visibility) AND (2) restrict existing line items in the quote from being edited.
Right now, even if a quote has been sent, the only way to restrict users from in-line editing the existing line items is by having two collections, one that displays with in-line editing when the quote has NOT been sent, and another collection that displays without in-line editing when the quote HAS been sent.
The easier solution would be to allow in-line editing for individual fields, upon certain criteria being met.
FYI As a workaround for now I’ve actually been using multiple collections on page just with different visibility settings to accomplish this conditional in line editing. I.e. I have a budget page for a project where inline editing is enabled in 1 collection when the project status is planning and editing disable when the project is active. I’m sure this is less efficient for both building and load time but it has worked very effective.
Yes that definitely works! I’ve done this, but if you want specific fields to be editable and others not, and you’re working with like 5-15 fields, then it becomes really inefficient to have 5-15 collections.
Bringing this up again… definitely a big bottleneck. I have various pages where I have many duplicated elements, one version with in-line editing enabled, and one version without in-line editing enabled.
This is to cover use-cases where data should only be edited when an item is at a certain stage, for example.
Stage-Based Use-Case:
I’ve designed a NL page to allow users to build a quote that will then be converted into a ‘Sent Quote’. Before the quote is sent, I want to give the ability to edit the fields, in line without an additional button press. After the quote is sent, I want to prevent any additional updates.
Permissions-Based Use-Case:
Managers should have the ability to edit certain in-line fields, while users do not, and vice versa.
Again, I find myself making workarounds (duplicate blocks like Joel describes/conditional action buttons) that I’m hoping I can avoid!
I’ve only got 1 or 2 conditions to watch for.