Vlocity ES DevOps Tools
Vlocity ES Tools (Beta)
==============
##### Disclaimer: This tool is not an offical tool from Vlocity or Salesforce. It was created with the intent of distributing certain uitlility tools, Use it at your own risk.
Clean Commands
- vlocityestools:clean:epcgkfix
- vlocityestools:clean:omniscripts
- vlocityestools:clean:templates
- vlocityestools:clean:cards
- vlocityestools:clean:datapacks
- vlocityestools:clean:savedomniscripts
- vlocityestools:clean:calcmatrix
- vlocityestools:clean:objects
Compare/ Report
- vlocityestools:compare:folders
- vlocityestools:report:dependencies:local
- vlocityestools:report:dependencies:remote
- vlocityestools:report:activeomniscript
SF Source
- vlocityestools:sfsource:createdeltapackage
- vlocityestools:sfsource:createdeltapackagelocal
- vlocityestools:sfsource:updatedeltahash
- vlocityestools:sfsource:createmocklwcos
Login
Data
- vlocityestools:data:upsert
CMT
- vlocityestools:jobs:executejobs
Copado
- vlocityestools:copado:copadomanifest
- vlocityestools:copado:copadolist
sh-session
$ sfdx plugins:install vlocityestools # Requires SFDX-CLI
`
#### Install with no promt:
sh-session
$ echo "yes" | sfdx plugins:install vlocityestools # Requires SFDX-CLI
`Usage
sh-session
$ sfdx vlocityestools:...$ sfdx vlocityestools:... --help
`
' 'Commands Info:
vlocityestools:clean:epcgkfix
Sync Global Keys between two orgs (from source to target org) for the descrived objects. If Duplicates are detected, Global Keys wil be updated.
Use -v,--check to only check and do not insert the records.
Notes:
- For now, this only works for CMT Package and without Product Versioning
- Please read carefully the documentation and check with the EPC implemtation team that this fits your needs and that the match Scenarios do apply for your implementation, Used it at your own risk.
- Avoid Using it in Production. Create a Full or partial copy if necessary.
#### Attribute Assignments Scenarios:
##### 1. Non Override Attribute Assignments (IsOverride__c = false )
This will Match Records to Sync the GlobalKeys by using a key generated by the combination of these two Values:
`
AttributeAssignment.vlocity_namespace__ObjectId__c.vlocity_namespace__GlobalKey__c
AttributeAssignment.vlocity_namespace__AttributeId__r.vlocity_namespace__GlobalKey__c
##### 2. Override Attribute Assignments (IsOverride__c = true )
This will query OverideDefinitions by using the considitions:
OverrideDefinition.vlocity_namespace__OverrideType__c = 'Attribute'
OverrideDefinition.vlocity_namespace__OverridingAttributeAssignmentId__c != null
OverrideDefinition.vlocity_namespace__OverriddenAttributeAssignmentId__c != null
And Match them across source and Target by the combination of these Values:
OverrideDefinition.vlocity_namespace__ProductHierarchyGlobalKeyPath__c
OverrideDefinition.vlocity_namespace__ProductId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionItemId__r.vlocity_namespace__ProductId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionItemId__r.vlocity_namespace__ContextProductId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionItemId__r.vvlocity_namespace__OfferId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__OverridingAttributeAssignmentId__r.vlocity_namespace__AttributeId__r.vlocity_namespace__Code__c
Then, Sync Global Keys of OverrideDefinition.vlocity_namespace__OverridingAttributeAssignmentId__c of source and target
#### Product Child Items Scenarios:
##### 1. Non Override Product Child Item (IsOverride__c = false )
This will Match Records to Sync the GlobalKeys by using a key generated by the combination of these two Values:
ProductChildItem.vlocity_namespace__ParentProductId__r.vlocity_namespace__GlobalKey__c
ProductChildItem.vlocity_namespace__ChildProductId__r.vlocity_namespace__GlobalKey__c
##### 2. Override Product Child Item (IsOverride__c = true )
This will query OverideDefinitions by using the considitions:
OverrideDefinition.vlocity_namespace__OverrideType__c = 'Attribute'
OverrideDefinition.vlocity_namespace__OverridingProductChildItemId__c != null
OverrideDefinition.vlocity_namespace__OverriddenProductChildItemId__c != null
And Match them across source and Target by the combination of these Values:
OverrideDefinition.vlocity_namespace__ProductHierarchyGlobalKeyPath__c
OverrideDefinition.vlocity_namespace__ProductId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionItemId__r.vlocity_namespace__ProductId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionItemId__r.vlocity_namespace__ContextProductId__r.vlocity_namespace__GlobalKey__c
OverrideDefinition.vlocity_namespace__PromotionItemId__r.vvlocity_namespace__OfferId__r.vlocity_namespace__GlobalKey__c
Then, Sync Global Keys of OverrideDefinition.vlocity_namespace__OverridingProductChildItemId__c of source and target
#### How to use a custom unique key for "OverrideDefinition" Match
You can pass as an additional parameter a .yaml file (-d ) to use custom unique key for "OverrideDefinition" Match sample File for PCI and AA.
Sample File:
yaml
PCI:
- namespace__ProductHierarchyGlobalKeyPath__c
- namespace__ProductId__r.namespace__GlobalKey__c
- namespace__PromotionId__r.namespace__GlobalKey__c
- namespace__PromotionItemId__r.namespace__ProductId__r.namespace__GlobalKey__c
- namespace__PromotionItemId__r.namespace__ContextProductId__r.namespace__GlobalKey__c
- namespace__PromotionItemId__r.namespace__OfferId__r.namespace__GlobalKey__c
AA:
- namespace__ProductHierarchyGlobalKeyPath__c
- namespace__ProductId__r.namespace__GlobalKey__c
- namespace__PromotionId__r.namespace__GlobalKey__c
- namespace__PromotionItemId__r.namespace__ProductId__r.namespace__GlobalKey__c
- namespace__PromotionItemId__r.namespace__ContextProductId__r.namespace__GlobalKey__c
- namespace__PromotionItemId__r.namespace__OfferId__r.namespace__GlobalKey__c
- namespace__OverridingAttributeAssignmentId__r.namespace__AttributeId__r.namespace__Code__c
`
USAGE $ sfdx vlocityestools:clean:epcgkfix -s -t [-p cmt] [-c] [-a] [-v]
OPTIONS
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins' (Optional)
-s, --source=source Source Org Alias or username
-t, --target=target Target Org Alias or username
-c, --pci=pci Match Product Chield Items GK
(Optional)
-a, --aa=aa Match Attribuyte Assigments GK
(Optional)
-v, --check=check Do not insert Updated Records
-d, --definitions=definitions YAML file Name to Override the
unique key for "OverrideDefinition"
Match
EXAMPLES
$ sfdx vlocityestools:clean:epcgkfix -s myOrg@example.com -t myOrg2@example.com -p cmt --pci --aa
$ sfdx vlocityestools:clean:epcgkfix --source myOrg --target myOrg2 --aa --check
$ sfdx vlocityestools:clean:epcgkfix --source myOrg --target myOrg2 --aa --check -d def.yaml
vlocityestools:clean:omniscripts
Delete old versions of OmniScritps and Integration Procedures and leave N amount of latest versions
Active versions will be ignored and wont get deleted.
USAGE $ sfdx vlocityestools:clean:omniscripts -u -n -p
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-n, --numberversions=numberversions Number of most recent versions of
OmniScrits to keep for each one.
Has to be greater than 0.
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
EXAMPLES
$ sfdx vlocityestools:clean:omniscripts -u myOrg@example.com -n 10 -p cmt
$ sfdx vlocityestools:clean:omniscripts --targetusername myOrg@example.com --numberversions 10 --package ins
vlocityestools:clean:templates
Delete old versions of Templates and leave N amount of latest versions.
Active versions will be ignored and wont get deleted.
USAGE $ sfdx vlocityestools:clean:templates -u -n -p
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-n, --numberversions=numberversions Number of most recent versions of
Templates to keep for each one.
Has to be greater than 1.
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
EXAMPLES
$ sfdx vlocityestools:clean:templates -u myOrg@example.com -n 5 -p cmt
$ sfdx vlocityestools:clean:templates --targetusername myOrg@example.com --numberversions 5 --package ins
vlocityestools:clean:cards
Delete old versions of Cards and leave N amount of latest versions.
Active versions will be ignored and wont get deleted.
USAGE $ sfdx vlocityestools:clean:cards -u -n -p
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-n, --numberversions=numberversions Number of most recent versions of
cards to keep for each one.
Has to be greater than 1.
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
EXAMPLES
$ sfdx vlocityestools:clean:cards -u myOrg@example.com -n 5 -p cmt
$ sfdx vlocityestools:clean:cards --targetusername myOrg@example.com --numberversions 5 --package ins
vlocityestools:clean:datapacks
Delete old DataPacks Used by Vlocity Build Tool
USAGE $ sfdx vlocityestools:clean:datapacks -u -p
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
EXAMPLES
$ sfdx vlocityestools:clean:datapacks -u myOrg@example.com -p cmt
$ sfdx vlocityestools:clean:datapacks --targetusername myOrg@example.com --package ins
vlocityestools:clean:savedomniscripts
Delete old Saved OmniScripts
USAGE $ sfdx vlocityestools:clean:savedomniscripts -u -p
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
EXAMPLES
$ sfdx vlocityestools:clean:savedomniscripts -u myOrg@example.com -p cmt
$ sfdx vlocityestools:clean:savedomniscripts --targetusername myOrg@example.com --package ins
vlocityestools:compare:folders
Compare two local Vlocity DataPacks folder
The output will be a CSV file with the results
USAGE $ sfdx vlocityestools:compare:folders -s - t
OPTIONS
-s, --folder1=folder1 Vlocity Folder 1 to Compare
-t, --folder2=folder2 Vlocity Folder 2 to Compare
EXAMPLES
$ sfdx vlocityestools:compare:folders -s vlocity1 -t vlocity2
$ sfdx vlocityestools:compare:folders --folder1 vlocity1 --folder2 vlocity2
vlocityestools:compare:packages
Compare Two Vlocity Metadata Folders. Gives Error if there is overlap
USAGE $ sfdx vlocityestools:compare:packages -s - t
OPTIONS
-s, --folder1=folder1 Vlocity Folder 1 to Compare
-t, --folder2=folder2 Vlocity Folder 2 to Compare
EXAMPLES
$ sfdx vlocityestools:compare:packages: -s vlocity1 -t vlocity2
$ sfdx vlocityestools:compare:packages --folder1 vlocity1 --folder2 vlocity2
vlocityestools:report:dependencies:local
From a local DataPack export foler, for Both OmniScript and VIP, 1st Level of dependencies:
- DataRaptors
- OmniScripts
- VIPS
- Remote Calls
- VlocityUITemplate
The output will be a CSV file with the results
USAGE $ sfdx vlocityestools:report:dependencies:local -f
OPTIONS
-f, --folder=folder Vlocity Folder Name
EXAMPLES
$ sfdx vlocityestools:report:dependencies:local -f vlocity
$ sfdx vlocityestools:report:dependencies:local --folder vlocity
vlocityestools:report:dependencies:remote
From remote Alias connection, for Both OmniScript and VIP, 1st Level of dependencies:
- DataRaptors
- OmniScripts
- VIPS
- Remote Calls
- VlocityUITemplate
The output will be a CSV file with the results
USAGE $ sfdx vlocityestools:report:dependencies:remote -u -p
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
EXAMPLES
$ sfdx vlocityestools:report:dependencies:remote -u SIT -p cmt
$ sfdx vlocityestools:report:dependencies:remote --targetusername myOrg@example.com --packageType ins
vlocityestools:report:activeomniscript
Check All OmniScrips are Active
USAGE $ sfdx vlocityestools:report:activeomniscript -u -p
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
EXAMPLES
$ sfdx vlocityestools:report:activeomniscript -u myOrg@example.com -p cmt
$ sfdx vlocityestools:report:activeomniscript --targetusername myOrg@example.com --package ins
vlocityestools:sfsource:createdeltapackage
Based on Vlocity Build Tool saved Hash in the Environment, Create Delta package for salforce.
Note: Only works for SFDX Source Format
--gitcheckkeycustom and --customsettingobject can be used to use a Custom "Custom Settings". For this: Create a new Custom Setting, the API name will be --customsettingobject. This Custom Setting will have two fields "Name" and the value of it will be the "--gitcheckkeycustom" and a field "Value__c" that will contain tha hash.
USAGE, $ sfdx vlocityestools:sfsource:createdeltapackage -u -d [-k ] [-p ] [-c -v ]
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-p, --package=package (Optional) Vlocity Package Type, Options:
'cmt' or 'ins'
-d, --sourcefolder=sourcefolder Salesfroce sorce folder name
-k, --gitcheckkey=gitcheckkey (Optional) Key when using gitCheckKey with Build Tool
OPTIONS IF USING a Custom "Custom Settings"
-c, --customsettingobject=customsettingobject (Optional) Optional Custom Setting API Object Name
-v, --gitcheckkeycustom=gitcheckkeycustom (Optional) Custom Setting record Name
-h, --valuecolumn=valuecolumn (Optional) API Field Name Where hash is stored
EXAMPLES
$ sfdx vlocityestools:sfsource:createdeltapackage -u myOrg@example.com -p cmt -d force-app
$ sfdx vlocityestools:sfsource:createdeltapackage --targetusername myOrg@example.com --package ins --sourcefolder force-app
$ sfdx vlocityestools:sfsource:createdeltapackage --targetusername myOrg@example.com --package ins --sourcefolder force-app --gitcheckkey EPC
$ sfdx vlocityestools:sfsource:createdeltapackage --targetusername myOrg@example.com --sourcefolder force-app --gitcheckkeykustom VBTDeployKey --customsettingobject DevOpsSettings__c
vlocityestools:sfsource:createdeltapackagelocal
Create Delta package for salforce based on HEAD and Input Hash.
Note: Only works for SFDX Source Format
USAGE, $ sfdx vlocityestools:sfsource:createdeltapackagelocal -h -d
OPTIONS
-h, --hash=hash Git Hash Value
-d, --sourcefolder=sourcefolder Salesfroce sorce folder name
EXAMPLES
$ sfdx vlocityestools:sfsource:createdeltapackagelocal -h f2a6eee1b509c3edd33ab070148be48e41242846 -d force-app
$ sfdx vlocityestools:sfsource:createdeltapackagelocal --hash f2a6eee1b509c3edd33ab070148be48e41242846 --sourcefolder salesforce_sfdx
vlocityestools:sfsource:updatedeltahash
When using a Custom "Custom Setting" Object for delta Package. You can update the hash in the environment using this command.
USAGE, $ sfdx vlocityestools:sfsource:createdeltapackage -u -p -d [-h ]
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-c, --customsettingobject=customsettingobject Custom Setting Object API Name
-v, --gitcheckkeycustom=gitcheckkeycustom Custom Setting record Name
-h, --customhash=customhash (Optional) Custom Hash Value to be updated
-a, --valuecolumn=valuecolumn (Optional) Custom Value Column
EXAMPLES
$ sfdx vlocityestools:sfsource:updatedeltahash -c DevOpsSettings__c -v DeployKey -u myOrg@example.com
$ sfdx vlocityestools:sfsource:updatedeltahash --customsettingobject DevOpsSettings__c --gitcheckkeycustom DeployKey --targetusername myOrg@example.com
$ sfdx vlocityestools:sfsource:updatedeltahash --customsettingobject DevOpsSettings__c --gitcheckkeycustom DeployKey --targetusername myOrg@example.com --customhash 0603ab92ff7cf9adf7ca10228807f6bb6b57a894
vlocityestools:clean:calcmatrix
This command will delete all rows of the Calculation Matrix Version based on the given ID as input. Then, it will update the version record with Dummy data so any other version can be Deployed. The Calculation Matrix Version can be delete after 24 hors due to Salesforce sweeper restrictions.
You can assign the user used to run this comnad a Permisison set or a profile that has the Bulk API hard delte to avoid the need of deleting the rows from the recycle bin.
USAGE $ sfdx vlocityestools:clean:calcmatrix -u -i -P
OPTIONS
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
-i, --matrixid=matrixid Matrix Version ID to be clean
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins'
-h, --hard Use Hard Delete
EXAMPLES
$ sfdx vlocityestools:clean:calcmatrix -u myOrg@example.com -i a0dR000000kxD4qIAE -p ins
$ sfdx vlocityestools:clean:calcmatrix --targetusername myOrg@example.com --matrixid a0dR000000kxD4qIAE --package cmt
vlocityestools:auth:login
Create an Alias using User and Password, (Token if needed as wells)
Note: This will not create an Alias with OAuth Connnection so the connection will expired.
USAGE $ sfdx vlocityestools:auth:login -u -p -a [-l ] [-t ]
OPTIONS
-u, --username=username Username to Autenticate
-p, --password=password Password
-t, --token=token Token
-l, --url=url Org Url, Default: https://login.salesforce.com
-a, --alias=alias Alias
EXAMPLES
$ sfdx vlocityestools:auth:login -u jgonzalez@vlocity.com.de1 -p 'pass123' -t eXUTfa9gpIxfaytnONqnlWFG -a dev1
$ sfdx vlocityestools:auth:login --username jgonzalez@vlocity.com.de1 --password 'pass123' --url 'https://test.salesforce.com' --alias dev1
vlocityestools:clean:objects
Delets SObjects from org defined by File. SOQL 'WHERE' can be specified
Sample File for EPC: (May not represent 100% EPC)
yaml
Objects:
namespace__OrderAppliedPromotionItem__c:
namespace__OrderAppliedPromotion__c:
namespace__OrderDiscountItem__c:
namespace__OrderGroup__c:
namespace__OrderDiscount__c:
namespace__OrderPriceAdjustment__c:
namespace__OrderMember__c:
namespace__OrderItemRelationship__c:
namespace__OrderProductRollup__c:
namespace__OrderRelationship__c:
OrderItem:
Order:
WorkOrder:
WorkOrderLineItem:
namespace__OrchestrationDependency__c:
namespace__OrchestrationDependencyDefinition__c:
namespace__OrchestrationItem__c:
namespace__OrchestrationItemDefinition__c:
namespace__OrchestrationItemSource__c:
namespace__OrchestrationScenario__c:
namespace__OrchestrationPlan__c:
namespace__OrchestrationPlanDefinition__c:
namespace__OrchestrationQueue__c:
namespace__OrchestrationQueueAssignmentRule__c:
namespace__OrchestrationSchedulerImplementation__c:
namespace__ThorOrchestrationQueue__c:
namespace__CompiledAttributeOverride__c:
namespace__OverrideDefinition__c:
namespace__AttributeAssignment__c:
namespace__ProductChildItem__c:
namespace__ObjectFieldAttribute__c:
namespace__ObjectElement__c:
namespace__ObjectFacet__c:
namespace__ObjectSection__c:
namespace__ObjectLayout__c :
namespace__ObjectClass__c:
namespace__UISection__c:
namespace__UIFacet__c:
namespace__PriceListEntry__c:
namespace__PriceList__c:
namespace__PricingElement__c:
namespace__Attribute__c:
namespace__AttributeCategory__c:
namespace__PicklistValue__c:
namespace__Picklist__c: namespace__CalculationProcedureVariable__c:
namespace__CalculationProcedureStep__c:
namespace__CalculationProcedureVersion__c:
namespace__CalculationProcedure__c:
namespace__CalculationMatrixRow__c:
namespace__CalculationMatrixVersion__c:
namespace__CalculationMatrix__c:
namespace__ProductAvailability__c:
namespace__ProductEligibility__c:
namespace__ProductRelationshipType__c:
namespace__ProductRelationship__c:
namespace__OpportunityLineItemRelationship__c:
namespace__Interface_ProductAttribute__c:
namespace__ProductConfigurationProcedure__c:
namespace__QuoteLineItemRelationship__c:
namespace__PromotionItem__c:
namespace__Promotion__c:
namespace__CatalogRelationship__c:
namespace__CatalogProductRelationship__c:
namespace__Catalog__c:
Product2: ProductCode like 'PHONE_%'
`
USAGE $ sfdx vlocityestools:clean:objects -u -p -d [-q true|false] [-r true|false] [-s true|false]
OPTIONS
-u, --username=username Username to Autenticate
-p, --package=package Vlocity Package Type, Options:
'cmt' or 'ins' (Optional)
-d, --datafile=datafile File with list Of Objects
-q, --onlyquery=onlyquery Dont Delete Any Object, just do queries.
Default: false
-r, --retry=retry Retry all Deletes if Error
Default: false
-s, --save=save Save Batch Results in File
Default: false
-h, --hard=hard Hard delete all records
This needs the System permission:
"Bulk API Hard Delete"
-t, --polltimeout=polltimeout Bulk API Poll time out in Minutes (Default 60)
EXAMPLES
$ sfdx vlocityestools:clean:objects -u myOrg@example.com -p ins -d objects.yaml
$ sfdx vlocityestools:clean:objects --targetusername myOrg@example.com --dataFile objects.yaml
$ sfdx vlocityestools:clean:objects --targetusername myOrg@example.com --dataFile objects.yaml -q true
$ sfdx vlocityestools:clean:objects --targetusername myOrg@example.com --dataFile objects.yaml -r true
$ sfdx vlocityestools:clean:objects --targetusername myOrg@example.com --dataFile objects.yaml -q true
vlocityestools:sfsource:createmocklwcos
Deploy Empty LWC for Missing OmniScript
USAGE $ sfdx vlocityestools:sfsource:createmocklwcoss -d -u
OPTIONS
-u, --username=username Username to Autenticate
-d, --datapacksfolder=datapacksfolder DataPacks folder
EXAMPLES
$ sfdx vlocityestools:sfsource:createmocklwcos -u myOrg@example.com -d vlocity
$ sfdx vlocityestools:sfsource:createmocklwcos --targetusername myOrg@example.com --datapacksfolder vlocity
vlocityestools:data:upsert
Upsert Data From CSV
USAGE $ sfdx vlocityestools:data:upsert -u -f -o -i
OPTIONS
-u, --username=username Username to Autenticate
-f, --csv=csv Path to the CSV File
-o, --object=object Object API Name
-i, --id=id API Name of the field to Upsert
EXAMPLES
$ sfdx vlocityestools:data:upsert -u myOrg@example.com -f accounts.csv -o Account -i Name2__c
$ sfdx vlocityestools:data:upsert --targetusername --csv accounts.csv --object Account --id Name2__c
vlocityestools:data:updatefield
Bulk Update a field with one value. Optional "WHERE" to filter records
USAGE $ sfdx vlocityestools:data:updatefield -o -f -v [-w ] -u
OPTIONS
-f, --field=field API Name of the field to update
-o, --object=object API Name of the Object
-u, --targetusername=targetusername username or alias for the target org; overrides default target org
-v, --value=value Value to update
-w, --where=where 'WHERE' to only update certain records (Optional)
EXAMPLES
$ sfdx vlocityestools:data:updatefield -u myOrg@example.com -o Product2 -f IsActive -v true
$ sfdx vlocityestools:data:updatefield --targetusername myOrg@example.com --object Product2 --field IsActive --value false --where "ProductCode LIKE 'VLO%'"
vlocityestools:jobs:executejobs
CMT Jobs Automation (Only for CMT Package). Based on the Jobs file, it will run then in sequence.
Sample Jobs File
yaml
jobs:
- 'jobdelete:vlocity_cmt__CachedAPIResponse__c'
- 'EPCProductAttribJSONBatchJob'
- 'EPCFixCompiledAttributeOverrideBatchJob'
- '{"methodName":"startProductHierarchyJob"}'
- '{"methodName":"clearPlatformCache"}'
- '{"methodName":"refreshPricebook"}'
- '{"methodName":"populateCacheCAJob","selectedList":["ContextEligibilityGenerator","GetOffersHierarchyHelper","GetOffers","GetContainOffers","GetPrices","GetOfferDetails"]}'##### Posible configuration:
#### Delete Records
'jobdelete:
#### Custom Apex Jobs:
'EPCProductAttribJSONBatchJob'
'EPCFixCompiledAttributeOverrideBatchJob'
#### CMT Admin Jobs:
'{"methodName":""}'
'startRootAccountJob'
'refreshBatchJobLists'
'refreshXLIBatchJobLists'
'resetInterfaceImplementations'
'mergeInterfaceImplementations'
'resetFieldMaps'
'startXLIBatchValidationJob'
'resetXLIBatchValidtionData'
'startAttributesBindingJob' // Aditional Parameters: 'objectNames');
'startRootProductChildItemJob'
'resetObjectMaps'
'createEpcObjectClasses'
'createEpcDefaultLayouts'
'deleteEpcDefaultLayouts'
'createDefaultPricingVariables'
'generateEPCGlobalKeys'
'startProductHierarchyJob'
'clearPlatformCache'
'refreshPriceBook' // Aditional Parameters: 'priceBookId'
'createDefContextualAdjData'
'startTranslationJob'
'loadDefaultObjectFieldsConfigMLS'
'startTranslationCacheJob'
'startConvertProductJSONToV2' // Aditional Parameters: 'convertProductBatchSize' and 'productFiltersListString'
'startConvertXliJSONToV2' // Aditional Parameters: 'convertXliInput', 'convertXliBatchSize' and 'xliFiltersListString';
'loadAPIMetadataCAJob'
'getCAJobList'
'populateCacheCAJob'
'startPopulateSellingPeriodDatesJob'
'populateMissingActionFieldInXLIs'
'startPopulateRequestedStartDatesJobs'
'startDeleteExpiredCacheJobs'
'startDeleteQuasiRecordsJobs'
'regenerateCacheAPIRecordsJobs'
'cacheMigrationJobs'
'getUpgradeData'
'startPopulateGKPathJobs'
'startUpdateEncryptAttrJob'
'createDefaultTimePolicy'
'startCreateRelationshipRecords' // Aditional Parameters: 'createRelationshipBatchSize' and 'createRelationshipHeaderFiltersListString'
'startReportNullSpecTypeBatchJob'
'startReportMismatchedSpecTypeBatchJob'
'startPopulateCatalogCodeBatchJob'
`
USAGE $ sfdx vlocityestools:jobs:executejobs [-j ] [-p ] [-s] [-m] [-l] [-u ]
OPTIONS
-j, --jobs=jobs Job File
-r, --remoteapex Use remote Apex
-m, --more Verbose logs
-p, --pooltime=pooltime Pooltime in seconds (default 10)
-s, --stoponerror Stop When Error
-u, --targetusername=targetusername username or alias for the target org; overrides default target org
EXAMPLES
$ sfdx vlocityestools:jobs:executejobs -u myOrg@example.com -j jobs.yaml -p 20
$ sfdx vlocityestools:jobs:executejobs --targetusername myOrg@example.com --jobs jobs.yaml --pooltime 20
$ sfdx vlocityestools:jobs:executejobs --targetusername myOrg@example.com --jobs jobs.yaml --pooltime 20 --remoteapex
vlocityestools:copado:copadomanifest
Creates Json for bulk commit a User Story in Copado
USAGE, $ sfdx vlocityestools:copado:copadomanifest -p [-n ] [-s]
OPTIONS
-p, --package=package Package.xml (or manifest.yaml when --vlocity) file location (required)
-n, --username=username Username to use (Optional, Default: "None")
-s, --vlocity Is a Vlocity Manifest (.yaml File)
EXAMPLES
$ sfdx vlocityestools:copado:copadomanifest -p package.xml
$ sfdx vlocityestools:copado:copadomanifest --package package.xml --username User123 --vlocity
vlocityestools:copado:copadolist
Creates Json to Bulk Update an User Story from a List of . Text File
USAGE, $ sfdx vlocityestools copado copadolist -m [-n ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
OPTIONS
-m, --manifest= (required) List.txt file location
-n, --username= Username to use
EXAMPLES
$ sfdx vlocityestools:copado:copadolist -m manifest.txt
$ sfdx vlocityestools:copado:copadolist --manifest manifest.txt --username User123