The fix of the issue is now available in the latest InDesign 2024(v19.5.0.084). We recommend you upgrade to the latest version for the fix.
Kindly update the data source file with the POSIX style path in Macintosh to work with data merge functionality smoothly. Please refer to the helpx https://helpx.adobe.com/in/indesign/using/data-merge.html to know more about the difference between HFS and Posix style paths.
You can get the actual POSIX path of a file by right-click it in the Finder while holding Option (or right-click, then press Option) > Copy as pathname menu. This can help you explore the correct POSIX paths to ensure you're using them correctly.
Note: Relative path as such /<foldername>/<filename> is no longer supported after the fix, as it considers the starting “/” as an absolute path. Instead, the recommendation is to omit the starting “/” and use <foldername>/<filename> instead or any of the other existing ways to access the relative path like ./<foldername>/<filename>.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right, and click on Check for App Updates.
—
Adobe InDesign Team
The fix of the issue is now available in the latest InDesign 2024(v19.5.0.084). We recommend you upgrade to the latest version for the fix.
Kindly update the data source file with the POSIX style path in Macintosh to work with data merge functionality smoothly. Please refer to the helpx https://helpx.adobe.com/in/indesign/using/data-merge.html to know more about the difference between HFS and Posix style paths.
You can get the actual POSIX path of a file by right-click it in the Finder while holding Option (or right-click, then press Option) > Copy as pathname menu. This can help you explore the correct POSIX paths to ensure you're using them correctly.
Note: Relative path as such /<foldername>/<filename> is no longer supported after the fix, as it considers the starting “/” as an absolute path. Instead, the recommendation is to omit the starting “/” and use <foldername>/<filename> instead or any of the other existing ways to access the…
I also had to revert to 19.3 for this to work.