Skip to content

Latest commit

 

History

History
47 lines (40 loc) · 2.11 KB

import-using-newman.md

File metadata and controls

47 lines (40 loc) · 2.11 KB

Import using NPM module newman

Prerequisites

 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

Importing to a different Adobe Organization

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:

  1. Create a postman_globals.json and add the unique settings as key value pairs

  2. Manually update the unique values after import

  3. Make edits to the import-tag.sh

    1. Optionally set ENVIRONMENT with your postman_environment.json
    2. Optionally set GLOBALS with your postman_globals.json
    3. Verify IO_COLLECTION path is correct
    4. Verify IMPORT_COLLECTION path is correct
    5. Set PROPNAME
    6. Set EXT_JSON path
    7. Set DE_JSON path
    8. Set all RULENAMES paths
    9. Set all RULENAMES_JSON paths
  4. Run

 ./import-tag.sh ./environments/myEnv.postman_environment.json 

You don't need to specify your environment if it's set in the script

  1. You will be prompted to enter the propID from the response above. Scroll up in the console and look for Create Property
    1. In the reponse test, you should see Property: 2022-11-01T20:01:47.017Z created with ID: PR69bad8d31cf7488daebace0c8dfb9679
    2. Copy and paste the ID back into the console and click Enter
  2. The Tag property will now successfully import into the specified property ID.