[Evergreen-dev] Fieldmapper usage for vendor making api calls

[Jason Stephenson]

XML-RPC is also an option. It has been a long time since I used it, but 
I was able to login and do things with it. The XML-RPC gateway returns 
objects with field names, IIRC.

It is available at https://host.domain.tld/xml-rpc unless you've 
disabled it in eg_vhost.conf.

On 10/11/23 08:54, Josh Stompro via Evergreen-dev wrote:
> Hello, I was working with Solus on some breakage of their app after our 
> upgrade to 3.11.  The issue was related to the fields ordering changing 
> in the results to service=open-ils.auth 
> method=open-ils.auth.session.retrieve.
> 
> When they initially set it up, they just went by the index number of 
> each result, but that changed due to actor.usr changes over the years.
> 
> I suggested that they could take a look at /reports/fm_IDL.xml for the 
> new ordering, and they quickly setup a system to grab that file every 24 
> hours and use it to access the fields for api results.  I just wanted to 
> double check to see if that is the recommended way to handle things if 
> they have customers with different versions of evergreen?  Is there a 
> simpler approach that would be better?
> 
> Thanks
> Josh
> Company logo	
> *Josh Stompro*
> IT Director
> stomproj at gsuite.larl.org <mailto:stomproj at gsuite.larl.org>| 218-233-3757 
> ext. 139| 218-790-2110
> *Lake Agassiz Regional Library *
> 118 5th ST S
> Moorhead MN 56560
> www.larl.org <http://www.larl.org>
> /Our mission is to enrich lives and strengthen communities./
> 
> 
> _______________________________________________
> Evergreen-dev mailing list
> Evergreen-dev at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev