If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
Reviews by other members of the community are marked by * in the last column.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
Reviews by other members of the community are marked by * in the last column.

I produce my monthly Review Report on OEX packages now for 18 months.
These are a view figures and some comments:

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
Reviews by other members of the community are marked by * in the last column.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
Reviews by other members of the community are marked by * in the last column.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
Reviews by other members of the community are marked by * in the last column.

I'm sure you have met this situation:

• There is a bug in a System that you can't reproduce yourself locally
• You need to run a few lines in the affected instance
• You get full access to System Management Portal
• But there is just no terminal, nor console, nor access with Studio, Atelier or VSCode
• How to run your few lines for testing ???

M:N Relationship is a recurring object of my interest for a long time.
So the subject turns up with me repeatedly.
For this article, I found a nice example with TWO separate M:N relationships. Some M:N².

It is not pure fiction but taken from a closer view of OEX Contests that we run on a regular base.

This package offers a utility to export an XLarge Global into a JSON object file and to show
or import it again. In a previous example, this all was processed in memory. But if this is a
large Global you may either experience <MAXSTRING> or an <STORE> error
if the generated JSON structure exceeds available memory.