discovered when changing shape of data sent to client but would also apply when changes/adds/deletes happen to objects already in the diagram so needs to be fixed.
Solution will be to only store object/field references (by name, not id so they can be exported across orgs) in persisted JSON diagram data
discovered when changing shape of data sent to client but would also apply when changes/adds/deletes happen to objects already in the diagram so needs to be fixed.
Solution will be to only store object/field references (by name, not id so they can be exported across orgs) in persisted JSON diagram data