Mike@Cirrius
My feedback
14 results found
-
13 votes
-
1 vote
-
10 votes
-
9 votes
An error occurred while saving the comment -
31 votes
An error occurred while saving the comment I'm running into a dependency deployment issue that throws this error: 'Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field' error.
Sadly, the apparent fix to this issue, per Salesforce (https://help.salesforce.com/s/articleView?id=000334872&type=1), is to add the MasterDetail relationship field BUT it cannot be added because it is flagged as "No difference". So I'm stuck!
UPDATE - To get around the No Difference Limitation, I physically had to modify the custom field so that it would pickup a difference. In this case, I tweaked the Field Description by adding a single period, ".". Seems ridiculous but this only applies for my specific use case.
-
1 vote
-
17 votes
-
2 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment We also use VersionOne in parts of our business in addition to JIRA. I'd like to see VersionOne be added to the integration list. Thanks in advance, Mike
-
35 votes
We're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
-
16 votes
-
1 vote
-
1 vote
-
1 vote
-
2 votes
We also have this need!
Here's the Use Case; We have an org that we've been monitoring for several months. Subsequently, we have logs for every day. It is incredibly time-consuming and cumbersome to have to open every single log in order to find in which logs a particular component(s) was altered. Ideally, it would be tremendously helpful to be able to search or filter these logs for a specific component or keyword similar to how we can filter/search within the comparison metadata. This feature would dramatically increase the ability to quickly and easily track down one or more daily logs which contained a reference to that component(s). The Monitoring Feature is already a huge help. Having the ability to quickly parse through them all would be a giant leap forward!
Thanks in advance for your consideration!