Loren D`Amico
My feedback
14 results found
-
1 voteLoren D`Amico shared this idea ·
-
4 votes
An error occurred while saving the comment An error occurred while saving the comment Loren D`Amico commentedI regularly run into this problem when trying to move apps, an object with it's lightning pages, etc.
Loren D`Amico supported this idea · -
3 votesLoren D`Amico supported this idea ·
An error occurred while saving the comment Loren D`Amico commentedHaving this one field fail can often creating a cascading effect of lots of things failing on the deployment which can be very confusing and frustrating. It would be much better to simply tell you up front that this one field won't be able to install because it's a duplicate.
-
1 voteLoren D`Amico shared this idea ·
-
1 voteLoren D`Amico shared this idea ·
-
3 votesLoren D`Amico shared this idea ·
-
2 votesLoren D`Amico supported this idea ·
-
2 votesLoren D`Amico supported this idea ·
-
4 votesLoren D`Amico supported this idea ·
-
4 votes
An error occurred while saving the comment Loren D`Amico commentedCurrently if you deploy a lightning page, even if it's activated org wide in the source org, it deploys not activated. The activation of the page should match in the destination org to what it was in the source org, or at a minimum there should be an easy way to make this happen.
Loren D`Amico supported this idea · -
2 votesLoren D`Amico shared this idea ·
-
3 votesLoren D`Amico supported this idea ·
-
4 votesLoren D`Amico supported this idea ·
-
3 votes
An error occurred while saving the comment Loren D`Amico commentedI often run into this issue when trying to move apps.
Loren D`Amico supported this idea ·
Here's some more examples:
Component [lst:dynamicRelatedList] attribute [relatedListApiName]: Could not find related list ... for entity ...
Field ... does not exist. Check spelling.
Something went wrong. We couldn't retrieve or load the information on the field: ...