agentturbo1 - Heyo, I'm using Version Control w...
Heyo, I'm using Version Control with some pretty good success. However our staging environment got messed some how and has some incorrect mappings. It's been awhile, but something along the lines of didn't recognize an existing worksheet for one of the worksheets so now it's just borked. We don't heavily use our staging environment so we've just left it alone, until now.
Can I somehow reset the mappings for staging clear out the staging org's content and just deploy a clean slate from dev -> stage? If so how so?
6 Replies
@Srikanth Jandhyala can you help here?
Any updates?
I sent the request again to the relevant engineering team. Waiting for an update from them.
@agentturbo1 can you create a support ticket for this? Would be helpful to get better response from the relevant team there..
will do! thank you!
@agentturbo1 , As part of the configuration creation, you can specify a mapping branch. If no branch is provided, the default mapping branch will be ts_config_files. In this branch, you will find a mapping file named <clusterIP>.mapping, which contains JSON files in the format <orgId>.json, where orgId represents the deployment organization in the cluster.
Opening the corresponding JSON file reveals a mapping between originalGuid and mappedGuid. To modify these GUIDs, deploy the object to the desired existing object.
Hey thanks for the response @Srikanth Jandhyala ! The problem is that I have 1 dev org guid that shows up twice in the staging mapping config. On top of that, both of those guids are referenced. One of them backs liveboard A and the other backs liveboard B.
When I deploy that object it will either only update one of them or create a new one again.
Obviously I'd prefer there to be one correct mapping and everything would be good.