Is there filter criteria on delivered FSM API's to return deleted records? For example criteria on the _generic list query of FSM_PayablesInvoiceDistribution to return deleted distributions.
Something like
mingle-ionapi.inforcloudsuite.com/.../_generic
Instance Selection can be modified to "include [only] deleted records". I've used that on list filter Instance Selection to view deleted records, though I'm not sure if that can be leveraged in an API call since it's not a condition. You might be able to specify the delete flag in the LPL filter, though I'm not sure how it would be formatted or if that's possible. I recall in ST you could filter SQL queries by DELETEFLAG, so that logical delete flag likely still exists in the DB.
I've never tried it, but based on Andy's suggestion, if you can create your own list that shows the deleted records you want within the normal Web UI (let's say you call it something super original, like DeletedRecordsList) then the IONAPI URL to access it would be:
mingle-ionapi.inforcloudsuite.com/YourTenantName/FSM/fsm/soap/classes/PayablesInvoiceDistribution/lists/DeletedRecordsList?_fields=_all (etc.)
Thanks Andy and Michael. You've got me pointed in the right direction. I'll see how far / close this gets me.
I'm able to create a list of deleted distributions as Andy described using "include only deleted records" in the instance selection portion of the LPL. In the ui, I'm able to view the list and correctly see deleted records.
I'm able to reference the list NB_DeletedDistributions in an API call as Michael described, but the call appears to ignore the Instance Selection clause in the underlying list LPL. (it returns non deleted records).
Similarly if I reference the list in Spreadsheet designer, it too ignores the instance selection specified in the LPL.
I speculated that the underlying user accessing the list doesn't have a role with the feature "Show Deleted and Future Records" but if that was the case then the results should be blank, not the non deleted records.
Any thoughts before I ask support if this is expected behavior.
