New answers tagged deployment
0
From your last updated comment it seems that you have run the test method but your hackClipDisburse() which is called is not having isTest qualifier I only see one on class.
4
To deploy a trigger to production , you will need to ensure your trigger has a test class and the class needs to cover at least 75% of the lines of code .
Looks like you are writing the trigger for first time .
I suggest you go through Salesforce trailhead content and learn some of the best practices such as below
bulkify your trigger
do not write soql ...
1
As linked in the documentation, the relevant Metadata API entity is Prompt. The Metadata API's documentation includes a complete sample package.xml manifest:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>Prompt</...
1
I wonder if all the Product2 custom fields being referenced exist in Production. If not they would need to deployed as well
1
After many hours trying to look for every single issue mentioned on this page, and getting so angry about the lack of useful error messages in DX I was reminded that deployment settings may give more info.
The error I was getting in DX was just
N/A duplicate value found: <unknown> duplicates value on record with id: <unknown>. The Path was ...
1
I ran into this issue on a Lookup field where it had the "Business Status" Field set to "Active" in the metadata. I was thrown off by the winter fix as it had a lookup filter.
I removed the Active from the field-meta.xml and that solved it for me.
0
Little late for the person who asked, but I just had to solve this issue the problem is if you don't bring the updated ReportType along with the new reports. It seems to throw this error.
You can include the ReportType in package.xml like this:
<types>
<members>ReportType_API_Name</members>
<name>ReportType</name>
<...
0
Found a simple trick to deploy dependent fields that are set from Include to Exclude using a package. With the dependent field set to "Exclude" on the dependency matrix simply deactivate and reactivate the (Excluded) picklist field value(s) from associated record type. Then retrieve your package again and when you deploy it will remove the fields from the ...
Top 50 recent answers are included
