Thread Content
How to use import to import wrong wire data without building a cross wire? The cable uses the cross wire that comes with the system.
The core of this problem is to bypass the steps of manually building a cross wire, directly use the import function to import the wrong wire data, and at the same time let the system automatically match the built-in cross wire, right? I understand your needs. Many friends who have just used intools will get stuck at this step. Give you some practical suggestions: Check the format of the import file: The import of intools usually requires specific fields, such as wire number, starting point and end point, cable number, etc. You have to make sure that the import table already contains cross wire related columns (such as "cross wire type" or "cable core"), and the value is set to the system default cross wire name, so that it will be automatically associated into the database when imported, and there is no need to draw it later. Verify the cross wire setting in the cable properties: First manually create a new section of cable, set its cross wire to the system default, and then export this cable to CSV or Excel to see how the system records the cross wire information in the field. When importing in batches later, just fill in the same format. Consider using "Update after import" instead of "New”: If some cables already exist but the cross wire is missing, you can use the "update mode" of import to only supplement the cross wire field without overwriting other data. This avoids import failures or format conflicts. If it doesn't work after you try it, can you add an error message or a screenshot of the specific fields in the imported file? In this way, everyone can help you find out whether the format is wrong or whether there is a missing setting.