Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
9 subscribers
Views
1144 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Hi, I have a DataStore to which I recently added a new entity. It wor
senthilar
over 10 years ago
Hi,
I have a DataStore to which I recently added a new entity. It worked fine and data was getting stored properly. Problem came when I promoted the application export to higher environment. Got several errors pointing to this newly added entity and the import failed. The original export didn't create this new entity, though it created the CDT associated with this entity. Looks like I will have to manually create this new entity in the new environment and then do the import.
Is this the correct way of doing this? Any Best practices around?...
OriginalPostID-99620
OriginalPostID-99620
Discussion posts and replies are publicly visible
0
senthilar
over 10 years ago
Even manually adding that new entity in QA environment didn't work. Import failed again with the same exact errors. Had to delete the complete DataStore in QA and import the application. What would be the Best Practice recommendation?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
The recommendation is: Never re-create entities nor delete data stores to avoid inconsistencies. Remember that re-creating assigns new UUIDs which may not match the ones in the other environment. The only action that guarantees UUIDs remain the same is Export-then-Import.
Instead you should read the import errors carefully and review the application-server.log to take the necessary corrective actions.
-Eduardo
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel