Closed robchett closed 2 years ago
Hi @robchett - do you know the customer ids of the brands under the LSL banner just so we can be sure this is applied to all configurations that will need it?
I believe they are YOM/RER/THA/LSI
Thanks - that tallies with what I've got here. We'll get this set up
I've added offices.oInetRm for YOM, RER, and THA I can't find LSI. Blocked while I look into where LSI are.
@gnthackray-reapit I think LSI might be an internal database so won't work with Platform. Just trying to confirm with our infra guys then I'll get back to you
Hi @robchett - I can't see that LSI are configured to use Platform services - would that align with your expectation? This has been set up for YOM/RER/and THA and you can access the data using the extrasField query string parameter on the offices endpoint ie
GET /offices?extrasField=oInetRM
and
GET /offices/{id}?extrasField=oInetRm
Ah, you are correct, LSI hasn't been moved to Foundations yet, I was under the impression it had been. Sorry.
Should I be able to see this now for YOM/RER/THA or is it after the next release?
That should be available now for those customer ids - it's just a configuration we have to enable rather than a code change. Any issues let me know
@plittlewood-rpt, can this be accessed on a property level instead of an office level?
I'm not seeing any additional data on GET /offices?extrasField=oInetRM
and GET /properties?extrasField=oInetRM
gives
"Access to one or more of the specified fields is not permitted. You must be granted access to this data beforehand"
It looks like you have commented on a closed issue. If your comment relates to a bug or feature request, please open a new issue, and include this issue number/url for reference. For more information on our processes, please click here
Request
In order for us to grant access to Semi-structured 'extras' field data, please provide the following information in this request:
Specification