- postman_environment.json file is configured and imported into postman
- Make sure to have Newman installed
npm install -g newman
- You have tag export files to import such as:
- myProject-extensions.json
- myProject-data-elements.json
- myProject-rulecmps-myRuleName1.json
- myProject-rulecmps-myRuleName2.json
If you are trying to import a tag property into a different organization than what it was exported from, there will be unique values that need to be updated. This can be done 2 different ways:
-
Create a postman_globals.json and add the unique settings as key value pairs
-
Manually update the unique values after import
-
Make edits to the import-tag.sh
- Optionally set
ENVIRONMENT
with your postman_environment.json - Optionally set
GLOBALS
with your postman_globals.json - Verify
IO_COLLECTION
path is correct - Verify
IMPORT_COLLECTION
path is correct - Set
PROPNAME
- Set
EXT_JSON
path - Set
DE_JSON
path - Set all
RULENAMES
paths - Set all
RULENAMES_JSON
paths
- Optionally set
-
Run
./import-tag.sh ./environments/myEnv.postman_environment.json
You don't need to specify your environment if it's set in the script
- You will be prompted to enter the propID from the response above. Scroll up in the console and look for
Create Property
- In the reponse test, you should see
Property: 2022-11-01T20:01:47.017Z created with ID: PR69bad8d31cf7488daebace0c8dfb9679
- Copy and paste the ID back into the console and click Enter
- In the reponse test, you should see
- The Tag property will now successfully import into the specified property ID.