...
Each template has three settings.
Setting | Usage |
|---|---|
on-update-keep-previous-value-if-null | True: If a cell is empty (null) the import will not overwrite the existing value in the database, it will be untouched. This is the default value if nothing is specified. False: If a cell is empty (null) the import will make the corresponding value in the database empty (null). |
config-name | This is the name that will display in the template selection drop down in the Manager. |
remove-macros | If true, import will create a temporary copy of the XLS file and remove all macros from that file before import is started. Set the value to false unless other needed, since removing macros may cause access rights problems on a server. |
| Info |
|---|
Macros in ExcelIn some cases macros can cause problems at import. If this happens ensure to set remove-macros="true". Please note that this setting may require changing access rights for the processes running the import. |
Options available to all presentations
| Info |
|---|
Version 5.3 and later |
It is possible to skip presentations if a cell contains a specific value, or include a presentation if a cell contains a specific value. This setting can be applied to all presentations and to part rows in assemblies.
| Code Block |
|---|
<ImportIf row="3" column="1" direction="Down" true-on-value="..01" default-value="false"/>
<SkipImportIf row="3" column="25" direction="Down" true-on-value="0" default-value="false"/> |
Excel parts import
Note! If row or column is set to 0, the value will not be used. So the below default config will actually not read any values and you will need to create your own config.
...
It is possible to add parts to a kit during import and thus use XLS import to create kits. A possible xls file to achieve this is according to this table.
Part number | Qty | Kit number |
|---|---|---|
123456789 | 1 | 987654 |
123456780 | 1 | 987654 |
123456781 | 2 | 987654 |
123456782 | 1 | 987653 |
123456783 | 2 | 987653 |
The configuration would then be like this.
...
From version 5.1 it is possible to import part assemblies as a list of assemblies and parts where a level column determines if following parts belong to an assembly. Eg below table will import two assemblies with 3 parts each.
Level | Identity | Name | |
|---|---|---|---|
| 1 | 1 | 10001 | Assembly 1 |
| 2 | 2 | 20001 | Part 1 |
| 3 | 2 | 20002 | Part 2 |
| 4 | 2 | 20003 | Part 3 |
| 5 | 1 | 10002 | Assemvly 2 |
| 6 | 2 | 20001 | Part 1 |
| 7 | 2 | 20004 | Part 4 |
| 8 | 2 | 20005 | Part!-- 5 |
| Code Block | ||
|---|---|---|
| ||
<!-- structure-level-enable="true" makes assembly import interpret level --> <ExcelPartAssemblyConfig on-update-keep-previous-value-if-null="true" structure-level-enable="true" remove-macros="false" config-name="Tana multilevel"> <Name row="2" column="8" direction="Down" culture="en-GB" /> <Identity row="2" column="4" direction="Down" /> <PersistentIdentity row="2" column="4" direction="Down" /> <PartRow on-update-keep-previous-value-if-null="true" part-ref-only-by-persistent-id="false"> <StructureLevel row="3" column="2" direction="Down" /> <Name row="3" column="8" direction="Down" culture="en-GB" /> <Identity row="3" column="4" direction="Down" /> <PersistentIdentity row="3" column="4" direction="Down" /> <PartNumber row="3" column="4" direction="Down" /> <Position row="3" column="3" direction="Down" /> </PartRow> </ExcelPartAssemblyConfig> |
...
| Filter by label (Content by label) | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|
...