View rule applying incorrectly on new record before being submitted

[Sam Ogden]

Hi All,

We are in the middle of making a large change to our change_request form.

This will see us no longer use some old fields and the addition of some new fields.  In order to handle existing changes I've made a view called 'legacy' and created a view rule:

This works for current records, however we use the change interceptor when 'create new' is selected from the application menu.  When I select normal change from the interceptor it is forcing the 'legacy' view until the form is submitted.  The interceptor link is setup:

I've also tried with setting the syparm_view=default but still having the same effect.  Any suggestions how I can get around this as I need all new change to use the updated form which is on the default view.

Thanks

Sam

[Jagadeesh R1]

Hello,

     try adding the line in the target URL to set the user preference to default 

     &sysparm_userpref.change_request.view=&sysparm_view_forced=true

[Sam Ogden]

Hi,

I've tried to amend, so my target URL is now:

change_request.do?sys_id=-1&sysparm_query=type= normal&sysparm_view=&sysparm_userpref.change_request.view=&sysparm_view_forced=true

But this is still causing the same issue, on selecting the normal change option on the interceptor it is going to the legacy view instead of default view.

Thanks

Sam

[Sam Ogden · Accepted solution]

Managed to get this working by amending the condition on my view rule:

I'm guessing that before the record is submitted although on screen the opened field is populated, in the back end it is not until submission.  Due to this it wasn't evaluating as I was expecting.