Repository navigation
Support and Maintenance
| Item | Maintained by |
|---|---|
| The 182 model definitions and their relations | MFGx, via the published accelerator |
| The generator that produces them from the Plex dictionary | MFGx |
| Corrections to the schema (as in 0.6.0) | MFGx, published as a new version |
| Item | Owner |
|---|---|
| Your Plex API credentials, quota and access | Customer |
| Noticing that Plex changed their API | Customer / implementing partner — see below |
The ExternalSystem record and site identity |
Customer / implementing partner |
| Which endpoints are enabled | Customer / implementing partner |
| Extraction flows, connections and scheduling | Separate package; implementing partner |
| Anything built on top of the landed data | Customer / implementing partner |
| Local modifications to the installed models | Whoever made them |
The models are a snapshot of Plex's published API documentation, taken on the dictionary date. Nothing Plex changes reaches an installed tenant on its own, and MFGx is not monitoring your Plex tenant or subscribed to their release notes on your behalf.
MFGx maintains the generator and publishes new accelerator versions when the dictionary is re-harvested. Deciding when to take one, and noticing that you need to, is yours. The Vendor Dependency sets out what each kind of vendor change looks like — the important ones are silent.
The models are generated, not hand-written. A local edit to an installed model is not preserved by an upgrade — the next version overwrites it, and the edit is silently gone.
If you need a field the accelerator does not provide, the supported route is a custom field on the model rather than an edit to a generated one. Custom fields are exposed on every model in this package for exactly that reason.
If you need a change to the schema itself, it belongs in the generator so it survives regeneration and reaches every site.
Include:
- The accelerator version and the model version on the tenant — they can differ.
- Whether the model exists, and whether the relation you expect is present in the introspected schema rather than in the model definition. Those come apart: a reverse collection can be declared and silently absent.
- The row's
sourceUrlandsourceVersionif the question is about data rather than structure. Those name the endpoint and the dictionary stamp that produced it.
- 40 sub-resource endpoints cannot be called — their URL needs more than one parent. They refuse rather than issuing a malformed request.
- 6 models have no reliable key and fall back to row position.
- Plex offers no pagination. 158 endpoints return their whole collection or nothing.
Each of these is listed rather than smoothed over because a limitation you know about is a plan, and one you discover in production is an incident.
Customer & Partner Guide v0.6.0