O$8.1.6: importing from JSON into lbs

[Alex Clay]

On Aug 28, 2018, at 16:01, Grzegorz (Greg) Pasternak <gpasternak at cogeco.ca> wrote:

>> This might be a good one to send to Omnis support. Can you extract this method and the sql file class to a sample library and see if exporting and importing it to JSON produces the same error?
>> 
> 
> First I would like to see if this can be resolved without bothering support.

To be clear, you're encountering a bug in Omnis. The expected behavior is that Omnis can take ANY library, export it to JSON, import it back, and produce the same library. Reporting bugs in Omnis should NEVER be a bother to Omnis Software Ltd. Reporting bugs helps ensure we get the quality development tool we pay for.

The bother, in my experience, is producing a reproducible test case. Fortunately, my experience has also been that issues with a JSON export or import are very easy to reproduce by simply copying code snippets to another library.

If you can isolate the problematic code, great. You can then find a workaround for this bug and move on with other work. If you can't determine a workaround, perhaps the list could offer a functional alternative that Omnis might like better on the import.

But that doesn't make Omnis any better for anyone else. Omnis isn't open-source, so you can't fix the root bug and submit a pull request to get it fixed. It's an enterprise tool, so you have to get Omnis Software to fix the bug. Moreover, you PAY for Omnis to fix the code so you DON'T have to submit pull requests to fix it yourself. I believe Omnis Software Ltd. would want the issue reported so they could fix it. I sure would love to have this fix for our own exports and imports, and I imagine many others would was the fix as well.

I'll step off the soapbox now, but please consider reporting this as a bug. Support is paid...by customers like you and me...to be bothered with bug reports. :)

Alex