wesley g dike
My feedback
4 results found
-
6 voteswesley g dike
supported this idea
·
-
20 voteswesley g dike
supported this idea
·
-
26 voteswesley g dike
supported this idea
·
-
4 votes
An error occurred while saving the comment An error occurred while saving the comment wesley g dike
commented
I agree, we do sandbox pilots for new territories prior to our 'go-live' for batches of our users in Field Service. We use Data Deployments to release the Field Service Configuration to prod once it is working as the new territories. There is a good mix of new and over lapping data in these deployments. It would be so much more comforting using the tool if I could see what the impact of the new territory deployment was going to be before I hit the 'Deploy Now' button.
We have backups but it isn't as easy to work with. Aren't CPQ deployments data? could they expand that functionality to Data Deployments allowing us to see 'comparisons' including New, Changed, No Change & Deleted similar to Meta data deployments? That would be a game changer for us.wesley g dike
supported this idea
·
Plus, I have had some unexpected scope creep from Seeding Data Deployments, where the deployment took ALL records instead of what I thought I had filtered on, due to how I had setup External Ids in the deployment. Being able to catch that prior to deployment would be great.