Record not Showing
When the database is used to manage multiple projects, make sure the records are bound to the project.
Asset not showing
It may be because it is requiring a project ID or that the asset tag record did not have a discipline allocated to it in the XLS file.
Asset Type is not linked to the asset tag
When importing a tag, it is important to make sure the tag links to existing asset types in the database. The XLS should have a column for asset type that is a summary field (e.g. PP – Pump), not just the asset type abbreviation.
Document not showing
It may be because it is requiring a project ID if the database is used to manage multiple projects.
If the document is a controlled document (see document type training), the document should have a document type summary column. The reason is that when importing a document it needs to know if the document is a controlled document or not. The document type should be a summary field (e.g. P&ID – Piping and Instrument Diagram).
Column with multiple Drawings
When importing drawings it is important to make sure the drawings are split into separate columns. If you receive an XLS file that has a column called drawings and it has P&IDs, Single Lines, you will be required to separate those into separate columns. Each column should have distinct column.
Column with value + Engineering Unit (EU)
It is important when mapping data into Smart Completions, that the administrator review where they are going to import the data. The columns of data that are targeted for importing must map to the correct data type format, for example:
Field not updated in Smart Completions
Make sure that the "overwrite" collision behavior is selected. Make sure the XLS source data can be imported into target field and format.
Asset list is not imported with vBOM import
When using vAssets import, BOM should be linked to the asset. Import BOM from the Assets import.