Has anyone encountered this on v42.0 and if so, was there a resolution? I am overriding the “New” Case action with a Lightning component.
Today I have been struggling trying to migrate reports and dashboards from developer organization to production. Looks like we can’t deploy dashboard without a folder. While for reports there exist standard ‘Unfilled Public’ folder, for Dashboard there is no predefined public folder.
When I tried to deploy the dashboard I kept receiving error
If I keep two criteria based sharing rules in Account.sharingRules XML file, there is a deployment error in start line of the the second rule: sharing operation already in progress.
I am trying to migrate object permissions using metadata deploy in workbench.I am facing an issue – although I have explicitly stated the standard object in package.xml, the object permissions are not present in zip file that gets downloaded in retrieve(All the object level permissions are set to false in source org for that object).
Here is my package.xml(I have included only contract):
While it appears that Salesforce supports backups of data & configs, it also appears that a complete backup is not possible. Have I misunderstood the meaning of this page?
I’m working on an application that consists of a base package and an extension package. Every time I update the base package in the development environment, I have to change the
<packageVersions> element in the metadata of some of the classes in the extension, so they use the latest version. Is it possible to specify that a class always uses the latest version of a package?
Though I am using flag BlockOnPossibleDataLoss=False in my Azure SQL Dacpac Deployment pipeline, it is ignoring the flag producing the following errors, Can someone suggest what I am missing-
I have an application in PHP/MySQL. I am searching for an automated way upgrading database behind the application.
I don’t need to have the compatibility with older versions once it is upgraded.
I’m trying to get a django site deployed from a repository. I was almost there, and then changed something (I’m not sure what!!) and was back to square one.