Joseph Kubon - 2 months ago
Hello! I've upvoted this Main/primary idea awhile ago, and now, all of the related Ideas for the specific standard objects too. Is that a normal process? Cause there are alot of standard objects - is this functionality being addressed one object at a time? </Insert Shocked Face Here/>
Jonah Mattox - 3 months ago
Wow, this update is super disappointing. This idea has been around for 14 years now and it is still in debate how it will be finalized and released. I've personally been waiting for this functionality for 7 years, and remember when it started to take shape at Dreamforce in 2017. But even with the parts that have gone GA now, it is still mostly unusable. Not having standard object support negates the value this could add. What is the point of showing how much more improved a custom object looks when Accounts, Contacts, and Opportunities are still the most critical and widely used objects in the system? This is a clear seam where end-users need a more seamless experience. To provide the latter, this feature is unusable.
Parik Dhody - 3 months ago
This sounds like Salesforce's way of slowing down on creating dynamic forms for standard object. If you really wanted a way to find out which standard objects to priortise - you could have simply put them into "Prioritization".
I think the community has spoken - we wany dynamic forms, there is no reason to now break this into:
- Do you want (or How many) want Account Dynamic form
- How many want Case Dynamic form
Get on with with Salesforce - Let's do them all and if you need help in priortization then chuck this into Priortization method not as seperate ideas.
Vin Addala - 3 months ago
Another quick update for everyone. Thanks to all the great feedback we received and I am happy to see so many have deployed on custom objects succesfully! We definitely hear you all when it comes to supporting standard objects for Dynamic Forms. It is definitely by far the top feedback we received and we had many discussions on this topic. Standard entities may have unique behaviors that we need to ensure are workign in the world of Dynamic Forms, as a result we have started working with the different entity teams. First step is we created a set of ideas tailored to each of the commonly requsted standard objects, so you can get updates directly from the team on its progress. We are still in the process of creating the rest of the ideas but, I wanted to get an update out ASAP.
Please follow these links to upvote and directly enage with the team assigned to it:
Nick Gibbons - 4 months ago
Having meant to experiment with the new Dynamic Forms feature for a while I finally got around to it. Starting with what I thought would be the most basic use case - hiding or displaying a field on the basis of the value of a different field - I was astonished to see that this results in a warning error dialog to the user each time that a visibility rule is triggered. So, yes, we now have dynamic forms (for custom objects) but ones that display what looks a lot to the average user like an error (the tooltip is even labelled 'Error') every time something dynamic happens. Whose idea of a good user experience is that?
I was so astonished by this I went as far as to log a support case to check that this was by design and could not be configured in any way. The have confirmed that is the case.