search

sfdx-isv / territory-management-toolkit

The Territory Management Toolkit (TM-Tools) is a Salesforce CLI Plugin that provides tools for simplifying the migration of a Salesforce org from Territory Management (TM1) to Enterprise Territory Management (TM2).
BSD 3-Clause "New" or "Revised" License
9 stars 0 forks source link

sfdx tmtools:tm2:deploy completed with warnings #23

Closed istvan-veeva closed 4 years ago

istvan-veeva commented 4 years ago

Hello,

I have run

$ sfdx tmtools:tm2:deploy

on one of my orgs but I received warnings, though the job was successfully completed:

=============================================================

? Deploy TM2 metadata using the above settings? Yes

Deploying TM2 Metadata... ✔ Prepare Environment for TM2 Metadata Deployment ✔ Deploy Main Group of TM2 Metadata

Running Post-Deployment Tasks... ✔ Query TM2 Org for Territory2 Record IDs ✖ Update Territory DevName Mappings ✖ Finalize Transformation of User/Territory2 Association Files ✖ Finalize Transformation of Object/Territory2 Association Files

Generating TM2 Deployment Report... ✔ Generate TM2 Deployment Report (/home/ec2-user/tm2.0/TM1/output/tm2-deployment.json)

Final Status
Deploy TM2 Metadata : TM2 metadata successfully deployed to the target org Post-Deployment Tasks : Warning - Some post-deployment tasks did not complete successfully (see above) TM2 Deployment Report : TM2 deployment report saved to /home/ec2-user/tm2.0/TM1/output/tm2-deployment.json Command Succeded : tmtools:tm2:deploy completed successfully, but with some warnings (see above)

=============================================================

Could you advice me what to check in order to rectifiy it?

Thanks, Istvan

VivekMChawla commented 4 years ago

@istvan-veeva If you look inside the TM2 Deployment Report JSON file it should provide additional information that can indicate what went wrong with the other steps.

Can you take a look or post selected portions of that file here?

istvan-veeva commented 4 years ago

Hi @VivekMChawla the issue was caused by hitting Salesforce governor limit regarding the number of territores supported per territory model:

"Exceeded the maximum number of territories per territory model."

Salesforce has now increased the limit so we should be ok. I am running the tool right now, no issue so far