| Info |
|---|
This article is a hybrid between Technical Documentation for a Solution and Workflow Documentation. Once each part has been elaborated on and defined enough to make sense on its own, it should be broken down appropriately. |
This document assumes the reader is familiar with Benchmark Lookups and the Conversion standard staging tables. We’ve documented the most common lookup groups and the tables they relate to in the following document Field Table to Lookup Table Relationships.xlsx
...
After staging the data into the staging tables, the Conversion Engineer checks which Lookups need to be maintained by looking at the Field Table to Lookup Table Relationships.xlsx for each of the tables staged.
...
Looking at Image 2, we have some source values (Column C) with no corresponding Benchmark values (Column B ), because they don’t exist on Benchmark (Image 3). So those rows would require some collaboration between the Configuration Engineers and the customer to determine how those would be configured in Benchmark. Upon determining that, the sheet can just be updated and reloaded with no logic update required!.
...
The LookupGroup Mapping steps should happen after the relevant data has been staged on the staging tables. Below we have a screenshot of the LookupGroup Mapper steps in a package.
...