Hi Khushboo,
Generally, project Common is a project where artifacts and functions are cross-projects. It’s also a default project, so you can create all other things in it if you have only one project and don’t want to care about project switching.
Common functions and artifacts can be accessed from all other projects. It will be confusing for you to have assets with the same name in Common project and any other project you are working on: which function/artifact you open (Common or current), which project artifact you select in command dropdown, etc.? That’s why we restricted name collision.
For example, if you have function F1 in project X1, you can create function F1 in project X2, because you can’t share these functions between these projects, so there will be no name collision.
However, If you have function F1 in project Common, you will be not allowed to create function F1 in projects X1 or X2 and vice versa.
So the same logic works for import to another project: if you select “Override” it means that it will continue to point to Common functions/artifacts with the same name and will override these Common assets.
If you want to have completely isolated functions and artifacts you should select the option “Keep both” instead of “Override” and provide more meaningful postfix for your assets (for example, _OGMS for the project from your previous ticket instead of _copy).
That way on import you will get everything absolutely isolated in this new project.
Please let us know if you have any more questions.
Regards,
Subject7 Team
Please sign in to leave a comment.