82 results found

1. Field Tracking Analyzer message is misleading

   If source org includes a new custom field with field history tracking enabled TRUE, the deployment analyzer reports the following when deploying to target org:

   'Fields with history tracking enabled cannot be deployed before it is enabled on the object. You should remove these history tracking changes from the deployment'

   Specific use case was object OrderItem

   1. Analyzer can clearly detect if field history is enabled on target org object (which it was) - message is spurious.

   2. Analyzer can arguably detect that target org's limit (20) will be exceeded by the deployment of the selected custom fields (which could add/remove field tracking from 1+ fields). In my use case, this was in fact the case so if analyzer is detecting this, the message should be reworded

   As an aside, what happens if org has purchased Field Audit Trail (where the 20 limit is not applicable).

   If source org includes a new custom field with field history tracking enabled TRUE, the deployment analyzer reports the following when deploying to target org:

   'Fields with history tracking enabled cannot be deployed before it is enabled on the object. You should remove these history tracking changes from the deployment'

   Specific use case was object OrderItem

   1. Analyzer can clearly detect if field history is enabled on target org object (which it was) - message is spurious.

   2. Analyzer can arguably detect that target org's limit (20) will be exceeded by the deployment of the selected custom fields (which could add/remove field… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Problem analysis and deployment failures  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Clarify installation of managed packages and allow opt-out

   It appears that if there are dependencies in the deployment that require a Managed Package to be installed/updated, that package is automatically installed/updated before the deployment takes place.

   This is great, but it needs more clarity and control for the user.

   It would be nice to know if Managed Packages are going to be installed as the result of a deployment, and if so, opt-in or opt-out of that process. It would be great if opting-out also displayed the related metadata with the dependency so those could be excluded as well.

   This may also avert some errors where metadata needs a Managed Package already installed in order to be deployed successfully.

   It appears that if there are dependencies in the deployment that require a Managed Package to be installed/updated, that package is automatically installed/updated before the deployment takes place.

   This is great, but it needs more clarity and control for the user.

   It would be nice to know if Managed Packages are going to be installed as the result of a deployment, and if so, opt-in or opt-out of that process. It would be great if opting-out also displayed the related metadata with the dependency so those could be excluded as well.

   This may also avert some errors where metadata needs… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Problem analysis and deployment failures  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating