Advanced Export Options is an
add-on. If you are interested in this, please contact us at
sales@pdmautomotive.com, we'll be happy to assist you.
To access the Advanced Export Options:
- Select the required Brand and click on Import/Export.
- Click Export.
- Select a Parts option and a Database. Click Next.
Here you can select between different Export options. You will find different Advanced Export Options within each Export selection you make.
Make a selection and click Next.
Excel/Advanced Export Options
- Toggle the Advanced Export Options switch to display options.
- Apply VCdb validation:
Only Export application records that are valid according to the Autocare VCdb.
- Expand Subconfigs Dynamically:
Expand your ACES file dynamically to always include values for subconfigurations that are used with at least one Make, Model, Year. This applies on a base vehicle (MMY) level. E.g. if you have selected a transmission for a 2005 Ford Mustang for one product, all other application records with the same base vehicle will also include transmission information.
- Expand Subconfigs Based on Selection:
Expand your ACES file based on the selected subconfiguration(s). By default, if you do not select any value when configuring ACES, all values are included. This Export Option will include all values if none is selected.
- Include PIES Attributes as Notes:
Attributes (of the PIES segment) will be exported as notes. Especially for product groups with identical fitment, this is helpful to overcome duplicates.
- Include Applications Based on Selected Filters:
Include just the vehicles as specified in the selected filters. You can select multiple filters.
- Include Applications Based on Vehicle Type.
- Include Implicit Results From Filter Selection:
Based on the filter you have selected you can either include (1) only applications that have the filtered value explicitly selected or (2) also include application records that have no selection for the particular value but based on the vehicle table do implicitly include the filtered value.
- Include Custom Vehicle Table for Validation:
Include a Custom Vehicle Table for the validation. PDM always only creates valid files. Entries that comply with your Custom Vehicle Tables would get filtered out. Include Custom Vehicle Tables into the validation to have those vehicles included.
- Only export managed attributes:
All managed attributes get exported (regardless of values existing for a part or not).
- Add validation in Export:
Add specific validation tags to the export.
12. Zip file:
Some vendors require that you submit files zipped or unzipped. This feature gives you the option to choose!
13. When you have made your selections, click on Export.
Export Builder Plus/Advanced Export Options
Toggle the Advanced Export Options switch to display options.
- Expand Subconfigs Based on Selection:
Expand your ACES file based on the selected subconfiguration(s). By default, if you do not select any value when configuring ACES, all values are included. This Export Option will include all values if none is selected.
- Expand Subconfigs Dynamically:
Expand your ACES file dynamically to always include values for subconfigurations that are used with at least one Make Model Year. This applies on a base vehicle (MMY) level. E.g. if you have selected a transmission for a 2005 Ford Mustang for one product, all other application records with the same base vehicle will also include transmission information.
- Apply VCdb validation:
Expand your ACES file dynamically to always include values for subconfigurations that are used with at least one Make Model Year. This applies on a base vehicle (MMY) level. E.g. if you have selected a transmission for a 2005 Ford Mustang for one product, all other application records with the same base vehicle will also include transmission information.
- Include PIES Attributes as Notes:
Attributes (of the PIES segment) will be exported as notes. Especially for product groups with identical fitment, this is helpful to overcome duplicates.
- Include Applications Based on Selected Filters:
Include just the vehicles as specified in the selected filters. You can select multiple filters.
- Include Applications Based on Vehicle Type.
- Include Implicit Results From Filter Selection:
Based on the filter you have selected you can either include (1) only applications that have the filtered value explicitly selected or (2) also include application records that have no selection for the particular value but based on the vehicle table do implicitly include the filtered value.
- Include Custom Vehicle Table for Validation:
Include a Custom Vehicle Table for the validation. PDM always only creates valid files. Entries that comply with your Custom Vehicle Tables would get filtered out. Include Custom Vehicle Tables into the validation to have those vehicles included.
9. Only export managed attributes:
All managed attributes get exported (regardless of values existing for a part or not).
10. Zip file:
Some vendors require that you submit files zipped or unzipped. This feature gives you the option to choose!
11. When you have made your selection, click on Export.
ACES/Advanced Export Options
1. Include Text Values for VCdb IDs:
ACES files by default do primarily include ID values (e.g. for Base Vehicles or Make and Model). This option will include text values that are represented by the IDs.
2. Exclude "Lang" Code for Notes:
Notes can be provided in different languages. You can decide if you want the language code to be included.
3. Expand Subconfigs Dynamically:
Expand your ACES file dynamically to always include values for subconfigurations that are used with at least one Make Model Year. This applies on a base vehicle (MMY) level. E.g. if you have selected a transmission for a 2005 Ford Mustang for one product, all other application records with the same base vehicle will also include transmission information.
4. Expand Subconfigs Based on Selection:
Expand your ACES file based on the selected subconfiguration(s). By default, if you do not select any value when configuring ACES, all values are included. This Export Option will include all values if none is selected
5. Include Qualifiers as Notes:
Qualifier values will be exported as a Note rather than a qualifier. If you cannot process qualifiers, this allows you to still capture the content.
6. Include PIES Attributes as Notes:
Attributes (of the PIES segment) will be exported as notes. Especially for product groups with identical fitment this is helpful to overcome duplicates.
7. Include Applications Based on Selected Filters:
Include just the vehicles as specified in the selected filters. You can select multiple filters.
8. Include Applications Based on Vehicle Type:
Include required applications based on the vehicle type.
9. Include Implicit Results From Filter Selection:
Based on the filter you have selected you can either include (1) only applications that have the filtered value explicitly selected or (2) also include application records that have no selection for the particular value but based on the vehicle table do implicitly include the filtered value.
10. Include Custom Vehicle Table for Validation:
Include a Custom Vehicle Table for the validation. PDM always only creates valid files. Entries that comply with your Custom Vehicle Tables would get filtered out. Include Custom Vehicle Tables into the validation to have those vehicles included.
11. Use EngineBase or EngineBlock/EngineBoreStroke:
Choose Engine Base or Engine Block.
12. Create Asset Records Based on AppAssets:
Create AppAsset records based on the included applications. An ACES file can contain three segments: (1) Applications, (2) Digital Assets associated to applications, and (3) AppAssets to define Assets to vehicle configurations. This Option will also include the AppAssets.
13. Exclude Equipment Data:
Export an ACES file including only Vehicle data instead of Equipment data.
14. Use delimiter to separate qualifier values of same type:
Group same vehicle application Qualifiers into one, and separate the values based on a character of your choice, except: ('), (<), (>), (&). Example: Engine Family Number (EFN): TGM2.4VXXXXX and Engine Family Number (EFN): TGM2.5XXXXXX can be combined into Engine Family Number (EFN): TGM2.4VXXXXX | TGM2.5XXXXXX if a Pipe (|) character was chosen.
15. Zip file:
Some vendors require that you submit files zipped or unzipped. This feature gives you the option to choose!
16. Click Export.
PIES/Advanced Export Options
1. Substitute PDM Digital Asset URL for file:
Use the PDM Server URL for your digital assets segment in PIES instead of the File name reference and separate file upload. Not intended to be used as a 'hot' link - only use to load images into target system.
2. Exclude Interchange Internal Notes
Exclude the Internal Notes from the Interchange segment when exporting a PIES file. These get excluded in general on the receiver side also.
3. Zip file:
Some vendors require that you submit files zipped or unzipped. This feature gives you the option to choose!