Entity Conflict Exception in ALM

Troubleshooting Guide

Cause

ALM allows you to add custom fields to your Tests, Resources, Test Sets and/or Runs. If any of these fields are defined as Required then values must be supplied when entities are added to ALM.

ALM returns a “Conflict” error if any mandatory fields are absent.

Solution

Provar allows you to supply default values for fields its ALM settings file. You need to define a default value for each mandatory field.

Identifying the fields

• Log into ALM with a user that has administrative rights.
• Click the cog icon to the right of the toolbar and then “Customize…”. This will open the “Project Customization” panel in ALM.

• Choose “Project Entities” from the navigation pane on the left. This will open the Project Entities tab.
• In the tree, locate the entity type indicated in Provar’s error dialog (e.g. Test) and open the User Fields sub-branch.
• Examine each field in turn and make a note of the Name for each with the Required checkbox checked. You will also need to note down a suitable default value for each field.

Once you have done this click the “Return” link to the right of the toolbar to exit the Project Customization screen.

Editing the ALM settings file

• Log into ALM if required and choose the “Test Resources” tab in the navigation pane on the left.
• Locate the “provarSettings” resource in the resources tree and click on it. It is directly under the top-most “Resources” entry.
• Click the “Download” button on the the “Resource Viewer” tab and save the file somewhere on your PC.

• Use a text editor (e.g. Notepad) to edit the downloaded file and carry out the following edits for each mandatory custom field:

1. Translate the field name as follows:

– remove the RSC_, TS_, CY_ or RN_ prefix from the field name (depending on the entity type)
– change all letters to lower case and all underscores (_) to dashes (-).

For example, RSC_USER_01 becomes user-01.

2. Add the following to the bottom of your provarSettings.xml (just before the closing ‹/provarSettings› tag) in your text editor:

‹customField entity=”{entity name}” name=”{translated field name}“›{default value}‹/customField›

Where:
– {entity name} is Test, Resource or TestSet as appropriate for your entity.
– {translated field name} is from step 1 above
– {default value} is a suitable default value for the field.

Your file might look like this at the end of your edits:

‹?xml version="1.0" encoding="UTF-8" standalone="no"?›
‹provarSettings›
   ‹disableCheckOut›true‹/disableCheckOut›
   ‹checkinAfterExport›false‹/checkinAfterExport›
   ‹initialExportStatus›Ready‹/initialExportStatus›

‹customField entity="Resource" name="user-01" initialValue="xxx"/›

‹/provarSettings›

• Save your edits, switch back to ALM and use the Upload button in the “Resource Viewer” tab to upload your updated file to ALM.

Testing the changes

• Switch to Provar and use the ALM Connect tool item to disconnect and then reconnect to to ALM. This will cause Provar to refresh its ALM settings.
• Re-try the operation that failed.