Creating Unique Values in Primavera Unifier
Setting up Unique Values in Primavera Unifier can help prevent users from entering values in a field that are duplicates of other records. It is important that uDesigner implementers know how to create unique BPs (Business Processes) that provide a foolproof User Experience to ensure accurate data entry and routing.
In this segment of the Making Primavera Unifier Foolproof series we are going to demonstrate how to create Unique Values in Primavera Unifier.
The purpose of creating Unique Values is to ensure the value on a field is unique across the company, or within the shell. Although the examples below are shown in Primavera Unifier version 10.1, this functionality will also work in earlier versions of Primavera Unifier.
Although the examples below are shown in Primavera Unifier version 10.1, this functionality will also work in earlier versions of Primavera Unifier.
Example Using Unique Values:
When entering a value for a Vendor ID, we want to make sure the user can not enter a value that is contained in another record for that field.
The Vendor ID must be unique. Since the Vendors BP is a company-level BP, it must be unique at the company level.
How This Was Built
- Line Item > Generic BP at company level
- Forms built with Vendor ID field as a Text Box
Dynamic Data Sets
Go to: Configuration > Business Processes > Vendors > Data Elements > Unique tab
Under Data Element select Vendor ID as a unique value at the company level
How It Works
We will demonstrate how Unique Values work in Primavera Unifier by attempting to create a new Vendor using an existing Vendor ID.
In the screenshot below you can see the Vendor ID for the vendor “DPrice Consulting” is 13579113.
When we attempted to create a new Vendor using this existing Vendor ID we were prompted with a Unifier Notification:
“The value for field Vendor ID must be unique. There is another record containing the same value for this field.”
Configuring this Data Element with a Unique Value has prevented the user from entering a Vendor ID that has been previously assigned to an existing Vendor, thus preventing an inaccurate/invalid data entry.