Setting up a common context can sometimes be tricky.
Here are some tips to help you troubleshoot issues you may be running into:
1. Fields must be present on the list view to be published.
- Any field you plan to publish has to exist on the source application’s list view. If the field is not configured on the list view, it will not be sent to the client and cannot be mapped forward.
- If you have extended a base application and need to use fields from the base app that aren’t visible, create an application layout to add them to the list view before publishing.
2. Make sure you are mapping the correct field.
- Use the publisher in the source application to confirm which field you are publishing from.
- Use the subscriber in the application to specify the field you are mapping from and the field you are mapping to.
- The source field does not need to match the destination field name. What matters is that the From Publisher Field (source application) and From Subscriber Field (destination application) match each other exactly.
Source Application
Destination Application
3. Make sure scopes match exactly.
- The scope on the source application must match the scope on the destination application. Any mismatch can break the common context.
4. Understand field naming, especially when joins are involved.
- The subscriber field is a free-text field because you may be receiving data from any field, not necessarily one with the same name. Because of this, accuracy matters. Type the subscriber field name exactly as defined in the publisher. If you are unsure, open the Help for the publisher field to see the correct field path formatting.
- If the source application contains table lookups,
_indicates a related field on a table lookup. - If the source application is over a join table,
$indicates the fields is on the secondary join table. - Examples when typing your subscriber field:
nsTestSecondaryTable$FieldName: Field directly on the table.nsTestSecondaryTable$TLFieldName_RelatedField: Related field from a table lookup field on the table.nsTestSecondaryTable$FieldName: Field directly on the secondary table.nsTestSecondaryTable$TLFieldName_RelatedField: Related field from a table lookup field on the secondary table. The screenshot below is an example of this scenario.
5. Use the Common Context Monitor.
- The monitor shows which publishers and subscribers are recognized and whether they are populated.
- If a publisher or subscriber doesn’t appear, it’s not configured correctly.
- If it appears but is not populated, you may have selected the wrong publisher field or typed the subscriber incorrectly.
6. When mapping multiple fields, start with one.
- Get a single field working first.
- Once it’s working end-to-end, add the remaining fields.
Note: An Interactive Report can also serve as the destination application. Anywhere I refer to the “destination application,” this also applies to Interactive Reports.