Texeï's plugin for sfdx
Home Page: https://texei.github.io/texei-sfdx-plugin/
License: BSD 3-Clause "New" or "Revised" License
Texeï's plugin for sfdx
Install plugin: sf plugins install texei-sfdx-plugin
Install the SF CLI.
Clone the repository: git clone https://github.com/texei/texei-sfdx-plugin.git
Install npm modules: npm install
Link the plugin: sf plugins link ./
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
When installing dependencies and the -k argument is supplied to specify the keys for each, if you have more than 9 packages / keys, starting with the 10th one the passwords are prepended with :
While importing "Name": "Richard Hendricks" in a Contact instead of "FirstName": "Richard", "LastName": "Hendricks", nothing was imported but the command didn't failed or displayed any error message.
Hi,
I like your plugin but am a bit confused about how to use package:dependencies:install command in my project.
I have my four unlocked packages (core, application-log, bypass-api and permission-set-groups), all of them installation key protected. Some of them are dependent on managed packages, no need to pass the installation key.
When I run
sfdx texei:package:dependencies:install -r -k "1:key1234 2:key4321 3:key2345 4:key3210"
I get an error
Installing package 04t3z000001gxxxxx2 : application-log 0.0.1.LATEST
ERROR running force:package:install: Invalid InstallationKey for SubscriberPackageVersion
ERROR running texei:package:dependencies:install: sfdx force:package:install --targetusername [email protected] --package 04t3z000001gxxxxx2 --wait 10 --publishwait 10 --noprompt` failed with code 1
It seems like the installation key wasn't picked for my unlocked package at all.
Am I using the notation for --installationkeys parameter correctly ? My understanding is that for first unlocked package it picks "1:key1234", for second it picks "2:key4321" and so on..
My sfdx-project.json
{
"packageDirectories": [
{
"package": "core",
"default": true,
"path": "./sfdx-packages/core",
"versionName": "Org's core - Pre-release One",
"versionNumber": "0.0.1.NEXT",
"dependencies": [
{
"package": "managed-package-1"
},
{
"package": "managed-package-2"
},
{
"package": "managed-package-3"
},
{
"package": "managed-package-6"
},
{
"package": "managed-package-4"
},
{
"package": "managed-package-5"
},
{
"package": "application-log",
"versionNumber": "0.0.1.LATEST"
},
{
"package": "bypass-api",
"versionNumber": "0.0.1.LATEST"
},
{
"package": "managed-package-7"
}
]
},
{
"package": "application-log",
"default": false,
"path": "./sfdx-packages/application-log",
"versionName": "Application Log - Pre-release One",
"versionNumber": "0.0.1.NEXT"
},
{
"package": "permission-set-groups",
"default": false,
"path": "./sfdx-packages/permission-set-groups",
"versionName": "Permission Set Groups - Pre-release One",
"versionNumber": "0.0.1.NEXT",
"dependencies": [
{
"package": "managed-package-1"
},
{
"package": "managed-package-2"
},
{
"package": "managed-package-3"
},
{
"package": "managed-package-6"
},
{
"package": "managed-package-4"
},
{
"package": "managed-package-5"
},
{
"package": "application-log",
"versionNumber": "0.0.1.LATEST"
},
{
"package": "bypass-api",
"versionNumber": "0.0.1.LATEST"
},
{
"package": "managed-package-7"
},
{
"package": "core",
"versionNumber": "0.0.1.LATEST"
}
]
},
{
"package": "bypass-api",
"default": false,
"path": "./sfdx-packages/bypass-api",
"versionName": "Bypass Api - Pre-release One",
"versionNumber": "0.0.1.NEXT"
}
],
"namespace": ""
}
Thank you.
Honza
Can you please help with how to push related files for the records?
By default, the installing an unlocked package compiles all code in an org. There are situations when this is undesirable or will block a deploy (like if two packages change together and leave things in a broken state until both are updated)
Please add support to pass through the --apexcompile flag to change this behavior during dependency install.
Just installed (which completed successfully) but received the following warnings:
warning texei-sfdx-plugin > @salesforce/core > @salesforce/ts-sinon > sinon >@sinonjs/formatio > [email protected]: This package has been deprecated in favour of @sinonjs/samsam
warning "texei-sfdx-plugin > @oclif/[email protected]" has unmet peer dependency "@oclif/plugin-help@^2".
Installing plugin texei-sfdx-plugin... installed v0.0.8
Any plans to add a license?
Hello, when exporting person accounts the name field is populated with the first name and last name. When importing this bring multiple errors as the system looks at it as you are trying to insert business account.
AccountRef2: INVALID_FIELD_FOR_INSERT_UPDATE-Account: bad field names on insert/update call: TestCustomField1__pc, TestCustomField2__pc
If I remove the Name field from those person account entities in the JSON all is good and I can import them to another org.
There is now a feature that can be added to the Scratch Org definition file to enable shared activities (SharedActivities).
Deprecate and add a message when running sfdx texei:sharedactivities:enable to warn users that they should move to the supported feature.
Currently there is no tests and no CI for the plugin, would be better to have some to secure updates and Pull Requests.
I have received this error a couple times using the sfdx texei:package:dependencies:install command
AppExchange Package is Deprecated, Details: The AppExchange package has been deprecated and can no longer be installed. Please try installing a newer version, or contact the package owner directly to resolve.
This occured not on a Appexchange package but rather just on one of my normal Unlocked package. I am not positive where it is pulling the package version Id from as in the latest instance in which I received the error, no package version in the history of that specific unlocked package had the same PackageVersionId as what the command tried to use (ie. it didnt use an old one)
I was able to manually install the error generating package using sfdx force:package:install. It was about the 5th package down in the dependency tree. Let me know if you need any additional info or anything was unclear
I noticed that the texei:package:dependencies:install command requires the DevHub to be specified. Is that really required?
@FabienTaillon, in my version of the command, it was simply because line 41 was set to true. Once I changed that to false, the command worked fine. I am not aware of a need in the Texei version to have access to the DevHub so I wanted to check with you first.
The use case where this becomes an issue is with customer admin teams trying to just deploy packages in bulk but they don't use a DevHub themselves.
Let me know if you have questions.
Cheers!
Hello!! We are trying to import records of Product, PricebookEntry and a custom object (also related to product) to a new sandbox.
For some reason we are not getting products with both related objects, instead products are duplicated. Some of them will have pricebook entry and the others will have the custom object.
-Edit: Since it is a sandbox, Product2, Pricebook2 and PricebookEntry are prepopulated on the refresh. So that might explain the duplicate values.
What we don't know how to handle is the import of the standard pricebook. Since we already have one in the sandbox, once we try to import another "standard" pricebook it will be isStandard=false, so we will get a "Before creating a custom price, create a standard price" Error. Can we somehow make this new pricebook standard or can we use as reference the existing pricebook?
Thanks!
Hi, is there any way for the command allornone consider all the requests, not just one by one.
Exporting Account... 1-Account.json saved.
Exporting Contact... 2-Contact.json saved.
Exporting Culture__c... 3-Culture__c.json saved.
Exporting Product2... 4-Product2.json saved.
Exporting PaymentCondition__c... 5-PaymentCondition__c.json saved.
Exporting Invoice__c... 6-Invoice__c.json saved.
Exporting Territory__c... 7-Territory__c.json saved.
Exporting Warranty__c... 8-Warranty__c.json saved.
Exporting Order... 9-Order.json saved.
For example if i had a problem in my Territory__c import i wanna to cancel all the imports....
Bonjour Fabien,
nous avons essayé d'utiliser votre outil pour générer facilement des données de tests dans nos ScratchOrg. Nous sommes cependant confronté à un erreur lors de l'étape d'import dans la ScratchOrg cible, malgré nos autorisations "full" en tant que System Administrator.
Avons-nous loupé quelque chose dans la configuration ou dans l'utilisation de la commande "export" ?
Le message d'erreur rencontré : Error importing record CompteRef1: INVALID_FIELD_FOR_INSERT_UPDATE-Unable to create/update fields: Name. Please check the security settings of this field and verify that it is read/write for your profile or permission set.(Name)
Merci d'avance pour votre aide !
I have 2 instances of vsc connected to the same sandbox (alias Personal). On my personal laptop, I can export data and import:
sfdx texei:data:export --dataplan ./dataFromProd/data-plan.json --outputdir ./dataFromProd --targetusername Production --loglevel=debug
sfdx texei:data:import --inputdir ./dataFromProd --targetusername Personal
From my work computer, the same export does not work. Status shows that it is exporting the first object and says done but no file is created and no error is shown (and it does not proceed to subsequent objects). Changing which object is first in the data plan does not change behavior.
setting the loglevel=debug is not providing any information to the terminal. Is it being written to a log?
When I copy the exported files from my personal laptop to my work computer and try the same import, I get an error:
ERROR running texei:data:import: The requested resource does not exist
again the loglevel=debug does not appear to be giving me any information
Starting with v47.0, the package install command will default the --securitytype parameter's from AllUsers to AdminsOnly.
In order to give users to ability to select the desired flag, the texei:package:dependencies:install command should accept and pass along the -securitytype flag and option
first off, thank you for this tool, it has made many things easier for me.
I am using the sfdx texei:sharingcalc:suspend command and wondering if there is any way to resume sharing calculations?
sfdx texei:sharingcalc:resume for example
When you try to export a standard PricebookEntry object like this:
sfdx texei:data:export --objects Pricebook2,Product2,PricebookEntry --outputdir ./data
there are no references in the generated PricebookEntry.json either to Product2 neither to Pricebook2 records. It contains just the following information, which is useless without those references:
{
"attributes": {
"type": "PricebookEntry",
"referenceId": "PriceBookEntryRef1"
},
"UnitPrice": 25000,
"IsActive": true,
"UseStandardPrice": false
},
Haven't you ever use this standard object in your work?
I think it is a bug and should be fixed. You can give me guidance about how to fix that or you can fix it by yourself. Thanks a lot.
P.S. In case you need more information: whenever you try to import the generated data into a scratch org, you are getting, obviously, an error like
Error importing record PriceBookEntryRef34: REQUIRED_FIELD_MISSING-Required fields are missing: [Pricebook2Id, Product2Id](Pricebook2Id,Product2Id)
which is obvious since we do not have such references in the original data file.
I've added ProfileId and UserRoleId fields to 1-User.json. I made sure Ids are accurate (querying destination org dynamically), but I am still getting this error: REQUIRED_FIELD_MISSING-Required fields are missing: ProfileId
Here's excerpt from 1-User.json:
"maps__ReceiveBatchExceptionEmails__c": false,
"maps__Version__c": null,
"disco__Youreka_License_Type__c": null,
"ProfileId": "00e4P000001adFTQAY",
"UserRoleId": "00EBZ000000HTE82AO"
Install command accepts wait parameter, but defaults to 10 minutes. This is different from the default 0 of the underlying sfdx command. Due to an issue with the ternary statement, passing in a wait of 0 is treated as a false, and the default 10 is applied.
I have cloned this repository and after going into this repo in my local and linking this plugin I have observed no sfdx texei commands are available.
Dir\user_id\Documents\sfdx_texei> sfdx texei:skinnyprofile:retrieve --help
» Error: command texei:skinnyprofile:retrieve not found
PS Dir\user_id\Documents\sfdx_texei> sfdx plugins
@salesforce/sfdx-scanner 2.12.0
texei-sfdx-plugin 1.14.0 (link) Dir\user_id\Documents\sfdx_texei
Appreciate your help!
User Story:
Working from home, I occasionally suffer from package loss and a step of my data push fails. My data is interconnected and changed by triggers, so I need to start from scratch. With an additional --retryOnFail (or --retry nTimes) option, I could prevent such a scenario.
The String field CodeTypologie__c equals to "044", during the extract using Data:Export command, the value on the Json file of the object equald to "44". Same for CodeSinistre__c
{
"attributes": {
"type": "Correspondance__c",
"referenceId": "CorrespondanceRef354"
},
"Name": "a063N000000uS0n",
"RecordTypeId": "SousTypeTache",
"CreatedDate": "2020-05-11T10:55:21.000+0000",
"CreatedById": "SfdxOrgUser",
"LastModifiedDate": "2020-05-11T10:55:21.000+0000",
"LastModifiedById": "SfdxOrgUser",
"CodePostal__c": null,
"CodeProduction__c": null,
"CodeSinistre__c": "31",
"CodeTypologie__c": "44",
"Equipe__c": null,
"LibSousTypeTacheP__c": null,
"LibSousTypeTacheS__c": "PROCEDURE",
"LibTypologie__c": "CONCLUSIONS ADVERSE",
"PGS__c": null,
"Type__c": "Sinistre",
"UGSH__c": null,
"UGSV__c": null
}
Hello,
Si on export des données via le plugin et qu'un champ Date est vide, alors le plugin met
"FieldName__c": ""
Lors de l'import, nous obtenons l'erreur : JSON_PARSER_ERROR-Cannot deserialize instance of date from VALUE_STRING value or request may be missing a required field at [Source: N/A; line: -1, column: -1][line:-1, column:-1]
Si le fichier est énorme, il est très compliqué de comprendre d'où ça vient, pour cela j'ai du passer par sfdx force:data:tree:export / import pour que SFDX nous donne la ligne en erreur.
Une fois le champ identifié, je suis obligé de l'exclure si jamais il est vide (même si je récupère plusieurs records où 1 seul à cette donnée vide).
Il faudrait pouvoir avoir la valeur null dans ce cas là, et corriger le message d'erreur afin d'indiquer la ligne en erreur.
Hi texei, i'm having a problem, the plugin is exporting the json of the data of one field with error.
The field have 14 chars in the maximum and is a text in salesforce and in the json the plugin is exporting like a number and without the zero in the beginning of the text.
Hi.
I'm playing around with SF packages CI/CD and some of packages contains dependencies to other packages.
How to properly provide latest version in sfdx-project.json so sfdx texei:package:dependencies:install would install it correctly? For now it will install older version even if latest version is installed already.
sfdx texei:package:dependencies:install{
...
"dependencies": [
{
"package": "PackageName",
"versionNumber": "1.4.3.LATEST"
}
]
...
}
> sfdx texei:package:dependencies:install -u myOrg -k "1:some_password"
Package dependencies found for package directory force-app
04t3Y000001QpjJQAS : PackageName 1.4.3.LATEST
Resolving dependencies... Done.
Installing package 04t3Y000001QpjJQAS : PackageName 1.4.3.LATEST
...
{
...
"dependencies": [
{
"package": "PackageName",
"versionNumber": "1.3.3.LATEST"
}
]
...
}
> sfdx texei:package:dependencies:install -u myOrg -k "1:some_password"
Package dependencies found for package directory force-app
04t3Y0000011MwvQAE : PackageName 1.3.3.LATEST
Resolving dependencies... Done.
Installing package 04t3Y0000011MwvQAE : PackageName 1.3.3.LATEST
...
Also RELEASED keyword is not working with texei plugin is it expected?
> sfdx texei:package:dependencies:install -u myOrg -k "1:some_password"
Package dependencies found for package directory force-app
ERROR running texei:package:dependencies:install:
PatchVersion=3 and BuildNumber=RELEASED ORDER BY BuildNumber
^
ERROR at Row:1:Column:225
Bind variables only allowed in Apex code
Resolving dependencies... done
Hi there,
Greate work so far, I love to use your tool, but I think it would be really cool to add a --saveRecordIds flag to the texei:data:export command.
Right now the old RecordIds are not saved in the jsons when exporting data, but i think it could be a benefit for some people (like me) to have the old Ids as well.
Since I have to handle some Ids that are just written as Strings in TextFields (and there is no possibility to make them a lookup) I have to use an additional custom field to map those oldIds to the new ones.
By having the oldRecordIds in the json as a property it would be really easy to create such a mapping.
Thanks
I just found this plugin command which seems perfect for our use case. However, when running it for a scratch org according to the instructions, the command throws the error in the title.
My command: sfdx texei:package:dependencies:install -k "1:MyPackage1Key 2:MyPackage2Key 3:" -w 30 -u "MyScratchOrgAlias"
The dependencies part of the sfdx-json looks like this (anonymized):
"dependencies": [
{
"package": "MyPackage1Name"
"subscriberPackageVersionId": "04t..."
},
{
"package": "MyPackage2Name"
"subscriberPackageVersionId": "04t..."
},
{
"package": "MyPackage3Name"
"subscriberPackageVersionId": "04t..."
}
]
From looking at the code, it looks the issue might be that our format for the sfdx-project file is different from what the command expects. How should I change it to prevent this issue?
When exporting AccountContactRelation, records being IsDirect = true shouldn't be exported as it's automatically created via the Contact.AccountId field.
Trying to import the exported file will fail because of duplicate value:
Error importing record AccountContactRelationshipRef1: DUPLICATE_VALUE-This contact already has a relationship with this account.(ContactId).
Today the workaround is to export data via a data plan excluding the direct relations:
{
"name": "AccountContactRelation",
"filters": "IsDirect = false"
}
When attempting to export records from the PermissionSetLicense table (in order to use them for a later import of PermissionSetLicenseAssign records), the following error is encountered:
ERROR running texei:data:export:
FROM PermissionSetLicense
^
ERROR at Row:2:Column:25
unexpected token: 'FROM'
Potentially this sObject is not available through the API being used?
We could not able to leverage filter part of the dataplan
log shows the data plan is not being considered while building the query
I have 2 package versions:
1.0.0.1 - Released
1.0.0.2 - Beta and "deleted" (deprecated using sfdx force:package:version:delete)
My package definition has a dependency like to following
{
"packageDirectories": [{
"path": "force-app",
"versionName": "",
"versionNumber": "",
"dependencies": [{
"package": "XXX",
"versionNumber": "1.0.0.LATEST"
}],
"default": true,
"package": ""
}],
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "51.0",
"packageAliases": {
"XXX": "0Ho......"
}
}
The specific dependency version autodiscovery should not include deprecated / deleted package versions since it is trying to install it since, technically is the latest in regards to version numbering, yet since it has been deleted and therefore doesn't even show in the sfdx force:package:version:list output, it should be filtered out
The recent addition of the -o ignore errors flag revealed an error I'm puzzled about.
When I run sfdx texei:data:import --inputdir ./SeedData -u $username locally, my seed script works. However, when I run the same command in our CI/CD pipeline I get an error that I believe indicates missing permissions.
Error importing record AccountRef1: INVALID_FIELD-No such column 'Global_Key__c' on sobject of type Account
Any thoughts on why this might be the case?
Several commands are ending with Error: EEXIT: 0 › Code: EEXIT. For instance, just run sfdx texei:data:import -h.
Looks like this is somehow linked to the returned object at the end of the command.
We only have a Standard Price Book and are not using custom Price Books. When exporting PB/Products and PB Entry, in the PriceBook2.json we have the Standard Price Book :
{ "attributes": { "type": "Pricebook2", "referenceId": "StandardPriceBook" }, "Name": "Standard Price Book", "IsActive": true, "Description": null }
When importing those files, a duplicate of the Standard Price Book is created. Is there a way to avoid this except manually deleting the PriceBook2.json file ?
After the import it's also impossible to pull from scratch org because of such errors :
Entity of type 'ListView' named 'PricebookEntry.Standard Price Book1617718301571' cannot be found
Thanks for sharing this plugin - looks very useful.
Context
I've just tried to run sfdx texei:skinnyprofile:retrieve in a project that has a default username but no dev hub. I also tried adding -u myDefaultUser, with the same result.
Expected
I expect this to execute the command against the default user, or against the user given by the -u flag
Actual
The plugin returns the error This command requires a dev hub org username set either with a flag or by default in the config.
I assume this is because requiresDevhubUsername is set to true in
Please consider changing this assignment so that the command does not require a DevHub for the project.
Hi Fabien, I'm trying to export the User object, but in the User.json i can't receive the profileId, and this field is required when i'll import the users on other org.
Since approx 1-2 weeks the command sfdx texei:package:dependencies:install --noprompt skips the installation of the default package. It used to be different and everything was installed on our fresh sandboxes.
The command only installs packages under "dependencies" like the "aepmocks" and skips the default "aepcommon":
No dependencies found for package directory aep-source/apex-mocks
Package dependencies found for package directory aep-source/apex-common
04t????????????????? : aepmocks 51.0.0.LATEST
Resolving dependencies... Done.
This is the sfdx-project.json:
{
"packageDirectories": [
{
"path": "aep-source/apex-mocks",
"default": false,
"package": "aepmocks",
"versionName": "aepmocks Spring 21",
"versionNumber": "51.0.0.NEXT"
},
{
"path": "aep-source/apex-common",
"default": true,
"package": "aepcommon",
"versionName": "aepcommon Spring 21",
"versionNumber": "51.0.0.NEXT",
"dependencies": [
{
"package": "aepmocks",
"versionNumber": "51.0.0.LATEST"
}
]
}
],
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "50.0",
"packageAliases": {
"aepmocks": "0Ho1?????????????",
"aepcommon": "0Ho1?????????????",
...
Versions:
sfdx-cli/7.92.0 wsl-x64 node-v14.15.3
texei-sfdx-plugin 1.9.3
I haven't found what the expected behaviour of sfdx texei:package:dependencies:install should be: install default package or not!?
I also tried different versions of @salesforce/core without any solution.
Which running "sfdx update", CLI showed a warning as below.
warning "texei-sfdx-plugin > @oclif/[email protected]" has unmet peer dependency "@oclif/plugin-help@^2".
The sfdx texei:skinnyprofile:retrieve command assumes the project filepath is force-app/main/default:
Many projects will use different filepaths or multiple package directories. Could ProjectPath be instead passed as a variable?
For example:
texei:skinnyprofile:retrieve -u MyScratchOrg --filepath packages/expensesApp/main/default
Having a Layout named [My Project] Awesome Layout on the org results in a file named Account-%5BMy Project%5D Awesome Layout in the repo.
The command will behave as if it's 2 different layouts and thus will delete it from the org.
I post here just in case someone has the same issue :) (maybe it can be added in documentation)
Default puppeteer embedded chromium does not work on alpine, so to bypass that, the following env variables must be set, and chromium must be installed using apk
RUN apk add --update --no-cache \
chromium \
nodejs \
npm
# Do not use puppeteer embedded chromium
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD="true"
ENV CHROMIUM_PATH="/usr/bin/chromium-browser"
ENV PUPPETEER_EXECUTABLE_PATH="${CHROMIUM_PATH}"Hi,
Really good DX plugin to manage the dependent packages! Big thumb up!!
If I run sfdx texei:package:dependencies:install twice, the command would install the dependent package twice. Shall we expect it detecting package already installed and skip?
You've got brand new easy to browse documentation, but there is no link to it from the main repo :)
You can add it in repository "About" section, and at the top of the README :)
example:
When using texei:package:dependencies:install and specifying -w 60 or --wait=60 plugin fails with the error:
ERROR running texei:package:dependencies:install: this.flags.wait.trim is not a function
sfdx texei:source:layouts:cleanorgwill output that approval page layouts are deleted, whereas they are not (and should not).
Hello,
When exporting records, all lookup fields referencing users are overwritten by the user Id who exports the data. Can this be avoided?
Thanks!
I have a cicd pipeline with salesforce/salesforcedx image. It is failing from last 2 days.
Can you please check by installing the plugin with the latest NPM and sfdx.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.