Issues with Internal Links after Importing XML Files into draw.io

[Tamtadam1]

Hello everyone,

I am currently working on a management system using draw.io that contains multiple pages, each with its own diagram. I have successfully implemented internal links that allow users to navigate between these diagrams. However, I am encountering an issue specifically when importing XML files that contain these links.

When I import an XML file, the internal links (formatted as data:page/id,) initially work correctly, but after a few seconds, they become invalid and display an error message stating that the link cannot be found. This behavior does not occur when I work with other formats, such as Excel files; the problem arises solely during the XML import process.

Here are some key details about my setup:

• I am using draw.io version [insert version if known].
• The XML structure includes [briefly describe the relevant part of your XML structure if necessary].
• I have verified that the IDs referenced in the internal links exist within the XML file after the import.

I would appreciate any insights or suggestions on how to resolve this issue. Is there a known limitation or specific handling of internal links during the XML import process that I should be aware of? Any help would be greatly appreciated!

Thank you!

[davidjgraph]

Possible Causes and Solutions for Internal Link Issues in draw.io XML Import

It sounds like you’ve set up your internal linking correctly, but there may be an issue with how draw.io processes XML imports. Below are some potential causes and solutions for your issue:

1. Ensure draw.io Version Compatibility

You mentioned that you're using draw.io version [insert version]. Some versions may have bugs or changes in how internal links are handled during XML imports. Try the following:

Update to the latest version of draw.io (if you're not already on it).
If you're already on the latest version, test the same XML file on an older version to see if the issue persists.

2. Validate the XML Structure

Since you've verified that the referenced IDs exist in the XML, the issue might be related to how the file is structured. A few things to check:

Ensure that the data:page/id, format remains intact after import.
Open the XML file in a text editor and look for inconsistencies in the <mxGraphModel> structure.
Compare a working and non-working XML file to identify differences.

3. Check for Post-Import Processing Issues

You mentioned that links initially work but become invalid after a few seconds. This suggests that draw.io may be reprocessing or "cleaning up" the imported data. Try:

Disabling auto-layout or other automatic processing settings in draw.io.
Checking whether the imported diagram works if you save it immediately after import and then reopen it.

4. Test Alternative Import Methods

If XML imports are causing issues but other formats (e.g., Excel) work fine, consider:

Converting your XML to an alternative format before importing (e.g., .drawio).
Manually re-adding one or two internal links after import and checking if they persist.

5. Try a Different Storage Location

Some web-based or cloud-synced versions of draw.io (e.g., the Google Drive version) may behave differently from the desktop app. If you're using an online version, try:

Importing the XML into the [desktop/web version] of draw.io to see if the issue persists.

6. Debugging with Console Logs

If you're comfortable with browser developer tools (for web-based draw.io):

Open draw.io in a browser.
Press F12 to open Developer Tools.
Go to the Console tab and look for errors when the links stop working.

Final Steps

If none of these solutions work, you may want to:

Share a minimal version of your XML file (removing any sensitive data) for others to test.
Contact draw.io support at the following location [insert location here].

Hope this helps! Let me know if you find any patterns when testing these suggestions.

[Tamtadam1]

Thank you!! This was the problem: "Some web-based or cloud-synced versions of draw.io (e.g., the Google Drive version) may behave differently from the desktop app"
Now when i'm using the app, it's working:
Kind regards Anders