Pro/INTRALINK 8.0 (and Windchill PDMLink 8.0), like Pro/INTRALINK 3.x, doesn’t allow two documents with the same name in the system. Typically, people encounter this restriction when checking in from the workspace. When you try to check in a new model in your workspace whose file name already exists in the database, your check in will fail because the “New object has name that already exists in database and database object is not checked out to Workspace”.

How can you see a “File name conflict” before checking in?

The “Compare status” field reports the “File name conflict” as soon as you save the model to your workspace. If you don’t see the “Compare Status” column in your workspace, you can add it to your View starting with “Select/Create Table View”.

How to check-in Pro/ENGINEER models that already exist in the Database

If you want to check in a model as the next iteration of the model that is already in Pro/INTRALINK – then you first need to “check out as link” the model – since you cannot check in anything if it is not checked out first. “Checking out as link” checks out the model without overwriting the “model file” in your workspace.

Solutions to Non-Unique Name Check In Conflicts

Different Model than the One in the Database Already

If the model in your workspace is really a different model than the one with the same name already in Pro/INTRALINK 8.0 – then you can rename the new model in your workspace to a new unique name and check in normally.

Same Model as the One in the Database Already

1. If you know which models in your workspace already exist in Pro/INTRALINK - in the workspace display, select those objects, otherwise choose select all, then choose check out.

2. In the checkout wizard – go to the second page of the wizard by choosing Next

3. Select all the objects in the list and choose the link (The icon that sort of looks like “||”)

4. This will result in the models being checked out – but it will not download the content to the workspace – meaning it will NOT overwrite the content in your workspace.

5. Now you can check them in since you have them checked out!

Scenarios When the Model in Your Workspace Is the Same as the One Already In Pro/INTRALINK

The following are the more common scenarios that will lead to a failed check in due to a non-unique name conflict where the model in your workspace is the same as the one already in Pro/INTRALINK.

1. Checking in a model that was already brought into Pro/INTRALINK 8.0

· Open a model in Pro/ENGINEER from disk

· Save the model to the workspace

· The workspace considers the models as “new” in the workspace

· Try to check in the model

· You get a name conflict error because the model already exists in the system

2. Checking in a model that is managed in Pro/INTRALINK but was modified outside Pro/INTRALINK.

· Add a Pro/ENGINEER model to your workspace from Pro/INTRALINK

· Back up the model to disk

· Open the model (from disk) in Pro/ENGINEER and save it to the workspace

· The workspace considers the models as “new” in the workspace.

· Try to check in the model

· You get a name conflict error because the model already exists in the system

3. Checking in a new model or models which have children that already exist in the system

· Load a dataset into Pro/ENGINEER from disk and save it to the workspace

· The workspace considers ALL the models as “new” in the workspace, even though only some of the models are new

· Try to check in the top level assembly

· Check in fails and you get a name conflict error because some of the child model already exists in the system

4. Checking in a model that was modified but was not checked out

· Add a Pro/ENGINEER model or models to your workspace from Pro/INTRALINK

· Modify the models

· This may happen when you attempt to modify a non-checked out model in Pro/ENGINEER and choose to ignore the prompt in Pro/ENGINEER to checkout the model

· Save the changed model to disk

· The workspace considers the models as “modified” but not checked out.

Now you should be good to go!