Import error: SyntaxError: JSON.parse: unexpected character at line 1 column 27 of the JSON data
We load this in MS Project and with https://app.ganttpro.com and seems to be loading fine, can you help us to pin point what the problem is as we dont have the source code of the bryntum jar reader, please?
Have you tried to export this file from MS Project when you open it there, and then import it to the Bryntum Gantt again? What is your MS Project version?
Reader sources are in Gantt/examples/msprojectimport/msprojectreader. Please read Gantt/examples/msprojectimport/README.md to learn how to build sources. The example is shipped with the prebuilt Gantt/examples/msprojectimport/msprojectreader/target/bryntum-msproject-reader-6.1.8.jar file.
I see that 4.1.0 is a beta, so is this going to be included in the 4.0.x or is it possible to apply this to the 4.0 branch? on the other hand the version referred it's not available anymore, is this because it's removed (not available in the customer zone)?
Not sure if you are saying that the msproject import fix is in the reader, if that's the case then we can get the nightly build and then compile the jar, is that what you are suggesting?
You can find nightly build with the fix available in the Customer Zone. The name of the zip you need, as example, is gantt-2021-01-27-next.zip
This fix will not be applied to versions 4.0.x, it will be available with official 4.1.0 release.
You can use files from nightly build and apply the fix by yourself.
Thanks for your reply, as we had to customize some of the ts files (as per one of the earliest post that we did regarding an effort calculation), do you know if the change is in the jar or the fix is in the javascript/typescript files? if it's with the "bryntum msprojectimport/msprojectreader/target/bryntum-msproject-reader-6.1.8.jar" then the upgrade using the nightly build will not be a problem for us, but if this is in the typescript/javascript files then doing the upgrade to an unstable version seems like a non workable solution for us at the moment, can you confirm where this fix has been applied to take a decision on how to upgrade?