Export/Import from JSON
Just a quick comment, that I had this issue, just trying to recall which
one it was…
We had issues with some oWrite external properties, and this required a
change from Michael to correct an internal issue… (ST/AD/093)
which he has now done, so that issue no longer remains with his later
Another issue I had, but has been resolved was with a line being greater
than 255 characters long… (ST/AD/087)
It seems a short line, so maybe a similar issue to oWrite is occuring
with oWorkbook, but if its Excel, I’m not sure how you might correct it.
Maybe Omnis support can confirm, and assist you with this.
They like small libs which replicates the error, so if you can do this
they will appreciate it, and find the problem quicker.
Based in Chester in the UK.
On 17/01/2018 13:40, An wrote:
> Hi Alex,
> I’ve added this to my .gitattributes.
> I’ve then removed my local JSON export files and tried to do the export from scratch. The previous error is gone but now I get a different error:
> Error code: 23470
> Error Text: Invalid method line – tokenising and untokenizing the method line does not result in the same text: Do oWorkbook.$initialize(kXLxls)
> Any experience with this error? I now have 176 errors like this?
> Met vriendelijke groeten,
> An Bayens
> Product Manager
> Stationsstraat 266, B-1700 Dilbeek
> T. +32 2 567 21 71
> Helpdesk: +32 2 568 14 54
> email@example.com <mailto:firstname.lastname@example.org>
> www.justsoftware.be <www.justsoftware.be/> | www.optimizegroup.be <www.optimizegroup.be/>
> <www.justsoftware.be/> <www.justsoftware.be/nieuws/531-kmo-portefeuille> <www.facebook.com/optimizegroupBE> <www.linkedin.com/company/optimize-group> <www.linkedin.com/company/optimize-group>
>> Op 17 jan. 2018, om 14:07 heeft Alex Clay <email@example.com> het volgende geschreven:
>> Hi An,
>> Omnis is picky about the line endings in the .omh source files. It wants CR or CRLF. Git will natively use LF on a Mac, and pulling an external change might cause the line endings to change to LF.
>> You can fix this by setting a .gitattributes file in your repository to specify CRLF line endings for omh file. I wrote up a guide on how to do this:
>> omnis.ci/guides/sharing-omnis-libraries-on-github.html <omnis.ci/guides/sharing-omnis-libraries-on-github.html>
>> Look under “Configure .gitattributes”.
>> I believe this is the cause of this error, but I might be wrong. Let us know if this fixes the problem.
>>> On Jan 17, 2018, at 05:26, An <firstname.lastname@example.org> wrote:
>>> Hi all,
>>> I’m trying to get the export/import from JSON to work but it doesn’t go as well as I expected.
>>> What I’m doing is I’ve opened my current library’s of my project (11 library’s) in Omnis 8.1.3. Then for each library I performed the action ‘Export Lib to JSON’. That goes all very well and creates 11 folders on my mac. Then via SoureTree I did a commit and push to bitBucket. So far so good.
>>> Then I created a branch in Sourcetree, I added a new window in my project in Omnis 8.1.3. Then I perform the action ‘Update JSON Tree’. Then I see my changes in Sourcetree and I can commit & push these changes to bitBucket.
>>> But then I changed some code (the title of my new window) directly in bitbucket en pulled these changes in to Sourcetree. That works as well but then I need to get those changes in Omnis Studio.
>>> I tried to do the action ‘Rebuild from JSON’ but then all of a sudden I get all kinds of errors.
>>> I get the message JSON Export completed with Errors:
>>> Error code 23522
>>> Error Text Error setting method text : .name (Unexpected error code:1)
>>> Result: It deleted my current LBS on my mac. Then I tried to do it via the action ‘New Lib from JSON’ that gives the same errors?
>>> Met vriendelijke groeten,
>>> An Bayens
>>> Product Manager
>>> Manage your list subscriptions at lists.omnis-dev.com
>> Manage your list subscriptions at lists.omnis-dev.com
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com