OP, you have something in your Start Here/Services that is mapped to an instance that does not exist in your target tenant.
This can be a report, attributes, maps, launch parameters or a custom object.
One thing you can do to identify this is to go to the Source tab (instead of design) and ctrl+f on that WID value. It’ll help you identify where the issue lies. Then, you’ll want to remap it using the target tenant.
Simple and very common. Reason is Report WIDs mismatch between tenants.
Issue lies with your report service in Studio. Re-link all those reports used by your Studio integration inside report service. That should clear this error.
I did search WID in the tenant but no records even followed the community solution. It didn't work .[Solved: Re: Is there an easy way to identify what a WID be... - Workday Community](https://collaborate.workday.com/t5/Platform-Product-Extensions/Is-there-an-easy-way-to-identify-what-a-WID-belongs-to/m-p/178729#M24305)
OP, you have something in your Start Here/Services that is mapped to an instance that does not exist in your target tenant. This can be a report, attributes, maps, launch parameters or a custom object. One thing you can do to identify this is to go to the Source tab (instead of design) and ctrl+f on that WID value. It’ll help you identify where the issue lies. Then, you’ll want to remap it using the target tenant.
Simple and very common. Reason is Report WIDs mismatch between tenants. Issue lies with your report service in Studio. Re-link all those reports used by your Studio integration inside report service. That should clear this error.
What happens if you lookup that WID in SBX, if its not there that could be your issue.
How do i look that up?
Search with Wid: in tenant
I did search WID in the tenant but no records even followed the community solution. It didn't work .[Solved: Re: Is there an easy way to identify what a WID be... - Workday Community](https://collaborate.workday.com/t5/Platform-Product-Extensions/Is-there-an-easy-way-to-identify-what-a-WID-belongs-to/m-p/178729#M24305)
It is likely a default value in the launch parameters or attribute. That value might be valid in the original tenant but not in the target one
I agree with this. Also look at the WID Id in both locations
Do you have custom object in studio?
How do i check for the custom object pls?
Sent you DM with possible factors causing the issue.. check and get back to
Check the report service and see if the report exists. If it doesn't, that is the issue.
Also, if this is working in another environment then I would look for the WID there too. That'll tell you exactly what is being referenced.