Smartstaff
1,385
edits
Changes
no edit summary
:: Bananas Ltd\
::: org_mandate.docx
An appropriate mapping file could look like the below. The unique identifier column being a reference to the unique identifier of each recordand the field id of where the files will be uploaded into.
{| class="wikitable" style="height: 134px;" width="534"
|-
||Unique Identifier
||Object
||Relative path + file name
||Field ID
|-
||12345
||Grant
||\grants\grant12345\grant_budget.docx
||2023123
|-
||12345
||Grant
||\grants\grant12345\grant_request.docx
||2023123
|-
||45678
||Grant
||\grants\grant12345\grant_budget.docx
||2023123
|-
||45678
||Grant
||\grants\grant12345\grant_request.docx
||2023123
|-
||4321
||Organization
||\organizations\Oranges Inc\org_mandate.docx
||1547893
|-
||8756
||Organization
||\organizations\Bananas Ltd\org_mandate.docx
||1547893
|}
===[[Custom_Field_Type:_Special_-_Advanced_Data_Table|Advanced Data Table]]===
<!--Ticket# 91363 - Imported L2 activities that are mapped to L1 XML fields are not displayed until the XML field is manually saved-->
Limitations when importing L2 records that will be displayed in L1 data table:
* The imported Advanced Data Table records are not displayed until the table is manually saved one time
* The syntax to display the Advanced Data Table records must be hardcoded and revised if the dependent XML field is ever changed versus using the @XML reference that will automatically include any changes
