Asset Records being Displayed as Global in Select List to relate Contracts to Software Licences

[Eugene Williams]

Has anyone come across where the Asset Records are all being Displayed as the name "Global" in Select List to relate Contracts to Software Licences and if so any ideas as to what has gone wrong and how to correct it pleease?

[Wind0004]

Hi Eugene, 

Have not come across this issue before.

Have done a quick check on a PDI and can see display names correctly in the demo data when relating assets to contracts on the asset workspace.

For us to best support could you provide some steps to replicate ? Or a screenshot of the issue.

Thanks

[Eugene Williams]

Hi and thanks for replying.

So the full story is as follows, 

I created back in Feb a bulk upload for our Contracts data and uploaded (Asset contract Table) them successfully into our Dev environment, then created some Asset / License Asset records all went well including the relating the Contract to the Software License Asset records. As we are going through the upgrade to Vancouver our Prod instance as known was used to overwrite. Dev, knowing that we tested everything fine previously I uploaded the Contracts and started creating the Asset License records in Prod, and now I get the attached screen shots below in both Prod and Dev.

[Wind0004]

Hi Eugene, 

Thank you for the context. It appears the data did get corrupted at some point , hard to judge when based on the above.

When you previously loaded the data from dev to prod , do you still have the data ? 

I assume it was via excel/import set and transform map ? 

my recommendation would be to re-load the  data again , but first test in dev or test instance before committing to production. 

If you do not have the data I would recommend you raise a hi-case to see if you can restore an instance to an earlier back up - and then export the data from there. ( would recommend an instance that is not part of stack like a dev 2 or staging ) 

Hope that helps. Please do let me know if this works for you.

Kind Regards,

Wind

[Eugene Williams]

Thanks Wind,

I have a feeling it was already an issue in Prod, and the problem came down to Dev during the cloning for the upgrade, we have an On-Prem instance so I've gone back to the team and they have registered a Hi Support case. Thanks again.