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
+1
person also asked this
people also asked this
Replies
3 replies
Subscribers
8 subscribers
Views
1825 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Deployment - Import a package from INT to UAT 'Duplicate names fo
ravib
over 11 years ago
Deployment - Import a package from INT to UAT
'Duplicate names for public and team groups are not allowed" - is the error due to which a couple of groups did not get imported....
OriginalPostID-65977
OriginalPostID-65977
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 11 years ago
Objects in Appian are identified by their UUID. In addition to this identifier, there are other objects such as groups and rules/constants that need to be unique in name.
If the developer doesn't keep this in mind, the issue you are seeing occurs. Basically this messages indicates that you have two groups with the same name, one in INT and the other in UAT but they are not the same object in terms of UUID. Therefore Appian is telling you that the group you are importing to UAT has the same name as a pre-existing group in UAT but with a different UUID.
You need to make sure your environments are in sync. If at some point a group gets deleted you need to reimport it from another environment to make sure it will be the same, instead of just creating a new one with the same name; a new group even if it has the same name, for the simple fact of being a new group will get a new UUID and be considered a completely different object.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 11 years ago
At this point you need to:
1. Decide which one is the group you want to use and make sure your models point to that one (delete the one you don't want to use and import the one you want to keep). There's a component here in Forum called Personalization Utilities which has a "Rename Group" custom smart service.
---> *** WARNING: Most likely your UAT environment is already using the pre-existing group, so deleting wouldn't be an option
2. Other option would be to rename the custom group in INT, this way you can keep both groups. The models from INT will use their group while the ones in UAT will use the other.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ravib
over 11 years ago
Thanks Edurado! It helped.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel