UI action > not possible to stay on record after update due to view rules ...?

Zod
Giga Guru

Hi all,

I'm on a form with a view forced via view rule ... . Now I have a UI action that will change the "reason" for the view to be forced to a value that will force an other view ... so after the update, I do not stay on the record (with the new view forced) as requested.

>>> action.setRedirectURL(current); at the end of the UI action does not work (most reasonable due to the forced view ... ). Any idea to workaround this issue?

Thank you!

1 ACCEPTED SOLUTION

Found a WORKAROUND ...


I just added required fields to the current view, that are only relevant if the phone type has been changed .. to I get the work done ... 😉


View solution in original post

9 REPLIES 9

stojdev
Giga Guru

If you have a view enforced by a rule, why would you want to override that rule from outside the view rule? What's the use case?



It sounds like you're contradicting your own view rules and the result is as expected.


... view is forced on the type of the device. But there are use-cases to change the type, that will require total different values to be set .. and displayed ... . so the view needs to be changed if the record type is changed ...


Perhaps you could share some screenshots on what you're trying to do



Not sure what you mean by "so the view needs to be changed if the record type is changed".


Would you like the view to change on the client when a user picks a new choice field value like in an OnChange Client Script?



Then you would need to trigger a form reload/refresh action.


A phone number is a phone number with all its fields that should be set - like if that number is to be used on an iphone too ...   - but if this number is to be used as a hunt group, totally different information is relevant - like the type of the huntgroup (broadcast, sequential etc.) ..


SO .. as the numbers are predefinded, it needs to be possible to convert them into a hunt group ... and stay on the form to add the required values ...


But as the view needs to be forces depending on the type ... this does not work.