Data Entities & Data Keys Notes - arp6333/xplusplus GitHub Wiki
When UAT is upgraded / refreshed
System Administration -> Data management -> Configure entity export to database
Click '_SQLDB' source name -> Validate
If encryption key is invalid, would need access to production. Navigate to the same path in Prod and click 'show' to copy & paste key into UAT.
- Repeat for the '_SQLDB_DEV' source, just add in '_DEV' to all '_SQLDB' strings.
When an existing Data Entity is modified
-
In UAT:
System Administration -> Data management -> Data entities
- Create new Entity, using the same selections of the modified entity with '_Temp' at the end of the name (or something just to denote it isn't the original)
- Click Modify target mapping -> Generate mapping
- Make sure all mappings looks valid, delete original entity, remove '_Temp' from name
-
Back to Data entities list
System Administration -> Data management -> Data entities
- Select created Entity
- Publish -> Click '_SQLDB_Dev' Source
- Publish (again)
-
Create new Export or modify existing Export job by removing and re-adding the entity as such:
System Administration -> Data management -> Export (if creating new)
System Administration -> Data management -> Select Export project in the Data projects section (if modifying existing)
- Set Group name and Description (if creating new)
- Remove entity (if existing)
- Add entity
- Target data format as '_SQLDB_DEV'
- Full push only, All fields, & Export across all companies
If 'Entity not published' error:
System Administration -> Data management -> Data entities
1. Select created Entity
2. Publish -> Click '_SQLDB_Dev' Source
3. Drop entity
6. Publish (again)
If that does not work, can also try:
vv ALWAYS IN DEV vv
1. Go to Prod SQL
2. Create backup of the data entity table in SQL: Select '_SQLDB_Dev' database -> Right click data entity table -> Tasks -> Export data-tier application
2. Drop the table
^^ ALWAYS IN DEV ^^
3. Repeat Create new Export step
- Run export job