The conversation is about a request for help in consuming JSON from an external system, the format of which does not match the usual format when importing through a custom service. A sample JSON is given and the question is asked whether it can be imported as it is or if a middleware to format it to F&O format JSON is required. Respondents suggest that there are several options — including modifying the current custom service to process the new format, creating a custom service to handle the new format, or using a logic app to pre-process the data to fit the format required by an existing customer service. In response to a query about expected format, and how the given one misses the F&O JSON requirement, it is explained that a custom service can be designed in any way to receive the JSON. They also observe that the JSON could have been incorrectly pasted since it contains many errors according to validators and suggest developing against a JSON schema from the provider or generating one. Another proposal is adding pre-processing with a Logic App or Azure Function to transform the data and then load it through OData, Rest API, or Recurring integrations. A participant reposts the code to make it readable and points out that there is nothing stopping them from building a custom service to handle the given JSON format, though a transformation could make processing it in F&O simpler.
Categories:
291,280
