Table of contents

• Introduction
• The use case
• The sending config
• The receiving config
• Read More

Introduction

This article will guide you though a concrete use case that will help you understand the concept of appending R-Field values in a source schedule's R-Field to another R-Field in a destination schedule.

The use case

Let's say you have a source schedule where R1 (alias MyRField) has this list of values (A, B, C, D) and in our activities we use values (A, B, C):

Let's further assume that we want to pass these on to an R-Field in a receiving schedule. In this example let’s say we want to pass them to R5 in the receiving schedule (i.e we want to append values to R5 that are not originally there, and ensure that A, B, and C will be in the list of R5 values).

The sending config

Here is how we can set up a sending config where we specify (in 2 below) that we want to export R1 (notice that the fieldname for R1 is called “uf_ref1” and alias is ‘MyRField’ – the latter must be specified in receiving config later).
Also notice that you can control (in 1 below) if you want only to upload used values (default), or all values in R1 (A, B, C, and D):

The receiving config

And here is how the receiving config can specify that the exported values for ‘MyRField’ shall be appended to R5 (referred to as hostfield 'uf_ref5' in dropdown selector):

Explanations:
1. This needs to be checked to allow R-Field updates (appending missing values)
2. If you want to transfer the name (label) of the original R-Field, this needs to be checked. Typically, “unchecked” since you normally do not want any source label to affect the label of R-Fields in your receiving schedule.
3. The label (alias) of the Source R-Field, spelled exactly as it is found in Safran source. This needs to be communicated between sender and receiver by some means.
4. Select which R-Field should receive the values.

Read More

How to append Safran R-Field values from Activity Code(s) in P6.