Is the functionality of dynamic view logic by design?
Hello! I love the Dynamic view as it allows users to edit existing data. But, how the logic function is causing a lot issues. Unlike in a form, where changing the value of a field instantly triggers the logic, the Dynamic View requires to hit save to trigger it. I hope this is not by design and it was just easier and faster to implement.
When you're updating a status, for example that require a date entry, once you saved the status field the date entry field appears but because it's required you can't change the status field back to a different status until you satisfy the required end date, even if it should be hidden at that point. Basically, you stuck between states. That's just one of the problems..
This functionality difference is especially confusing for our users when we use both forms and dynamic view. Does anyone know if this is by design or it is on the roadmap to achieve parity with forms?
Or maybe I'm the only one having this issue?
Tx
Answers
-
Nvm, I found the answer:
Categories
- All Categories
- 14 Welcome to the Community
- Customer Resources
- 64.9K Get Help
- 439 Global Discussions
- 138 Industry Talk
- 471 Announcements
- 4.9K Ideas & Feature Requests
- 129 Brandfolder
- 148 Just for fun
- 68 Community Job Board
- 488 Show & Tell
- 33 Member Spotlight
- 2 SmartStories
- 300 Events
- 36 Webinars
- 7.3K Forum Archives