Catalog items view change after upgrade from Washington DC to Yokohama

[architect]

Hey Everyone, 

Posting as I have been unable to pinpoint what is causing this. I am testing an upgrade from Washington DC to Yokohama in my dev instance. I noticed that when we develop new catalog items in Yokohama, their view is vastly  different in the service portal than they are in Washington DC. I have tested with multiple catalog items and am impersonating a normal user without roles.

Yokohama Instance:

Same catalog item update set exported and imported into our test instance on Washington DC:

Does anyone know what may be causing this? We rely heavily on the service portal and I won't be able to proceed with the upgrade unless we can get this resolved.

Thank you!

  

[Dr Atul G- LNG]

Hi @architect 

Two things:

1. Try to repair the portal plugin.

2. Try clearing the cache and then check again.

If it still doesn't work, log a new support case, and the team will assist you.

[Robert Laudani]

Thanks for the suggestions, I have already tried them both without luck. 

I noticed the URLs were different, I also recently enabled Now Assist in my dev instance. It seems Now Assist search is the culprit as I am taking the same steps in both instances portals search to locate the same catalog item in both environments. If I merely change the URL of the correct catalog item to the instance that was updated I am shown the correct view. I have opened a support ticket with SN and will update once we have a resolution. 

[Dr Atul G- LNG]

Hi @Robert Laudani 

I doubt Now Assist has something to do here , let wait for SN to come back.

[Sue L]

We noticed that it shifts the related list, but does not affect the form... just a different view.  Not a concern to us.  It is the difference between using new Employee Center & Service Portal, which we were already migrating to Employee Center.