It would be a huge timesaver to have an endpoint that returns entity_ids of entities that have changed since a particular point in time.
Something like a (paging) endpoint that accepts an xs:dateTime as param would be ideal, returning a dict or map of entity_ids that were subject to change since that point in time.
/api/entities/changedsince/yyyy-mm-ddThh:mm or whatever you deem appropriate.
Reasoning: Currently I do
iterate over all entities in MPR and (re-)export everything,
transform the JSON to our MRP standOff.xml output
commit the resulting changes, which might only affect a few entities
huge time and electricity overhead for no good reason
It would be a huge timesaver to have an endpoint that returns entity_ids of entities that have changed since a particular point in time.
Something like a (paging) endpoint that accepts an
xs:dateTime
as param would be ideal, returning a dict or map of entity_ids that were subject to change since that point in time./api/entities/changedsince/yyyy-mm-ddThh:mm
or whatever you deem appropriate.Reasoning: Currently I do