Foresee Consulting Creating Collaboration to Contain Costs

Making Primavera Unifier Foolproof – Dynamic Data Sets

Creating Dynamic Data Sets in Primavera Unifier

In this segment of the Making Primavera Unifier Foolproof series we are going to demonstrate how to create Dynamic Data Sets (DDS) in Primavera Unifier and why they are useful when configuring various business processes. Although the examples below are shown in Primavera Unifier version 10.1, this functionality will also work in earlier versions of Primavera Unifier.

What is a Dynamic Data Set?

Dynamic Data Sets (DDS) allow users to:

  • Limit values in one field, based on the value in another field or fields
  • Change field properties (editable, read-only, required) for a field, based on the values in another field

Dynamic Data Sets consists of a Master Data Element, Value Set and/or Behavior Set

Master Data Element – A Data Element (DE) on a form that controls the behavior and available values of other DEs.

Allowed for data elements based on:

  • Pull-down Menu
  • Radio Button

Value Set – The fields on a Dynamic Data Set with values limited by the Master Data Element

Behavior Set – The fields on a Dynamic Data Set with behavior controlled by the Master Data Element

These fields are either:

  • Required
  • Disabled (read-only)
  • Editable

Example using Dynamic Data Sets:

In this example we are going to show you how you can build a Dynamic Data Set to control the available value options for a specific field.

We will use the example of a business process where selecting a Country field will limit the values available to the user in the corresponding State/Province field.

We will also set this up so that the Other field becomes required if a combination of Country and State is not valid.

Example Without DDS

In the example below you can see a business process that includes fields for Country and State/Province. Without a Dynamic Data Set you can see there are no limitations to which State/Province values can be chosen for a specific country.

Screenshot of Primavera Unifier business process without use of Dynamic Data Sets

The values selected in the form above may not make sense to a user, but is perfectly acceptable to a database.

Example With DDS

With the Dynamic Data Set applied the user is only allowed to choose a State/Province that is applicable to the selected Country. Because this combination is valid, the Other field is NOT required.

Screenshot of Primavera Unifier business process with proper use of Dynamic Data Sets

 

How This Was Built

Vendors BP

  • Line Item > Generic BP at company level
  • The forms are built with State/Province and Country as pull-downs with the Other field as a text box.
  • Country set as a required field
  • State/Province and Other as editable

Building the Dynamic Data Set

Built in Data Structure Setup > Dynamic Data Sets

  • Country pull-down assigned as the Master Data Element
  • State/Province pull-down assigned as a Value Set field
  • Other assigned as a behavior set field

 

Creating the Master Data Element

Primavera Unifer Business Process - Master Data Element

 

Creating the Value Set

Primavera Unifer Business Process - Value Set

 

Creating the Behavior Set

Primavera Unifer Business Process - Behavior Set

 

DDS Applied to the Form

Applying DDS to Vendors BP in Unifier Screenshot

Assigning Dynamic Data Sets to Vendors BP in Unifier Screenshot

 

Creating Dynamic Data Sets in Primavera Unifier can significantly decrease the possibility for a user to enter incorrect or invalid data. It is important that uDesigner implementers know how to create business BPs that provide a foolproof user experience to ensure accurate data entry and routing.

 


Explore the Entire Making Primavera Unifier Foolproof Series