架构更新验证使Azure逻辑应用程序失败 [英] Schema update validation fails Azure logic apps

问题描述

在我的逻辑应用程序中，我正在使用HTTP触发器，该触发器每3小时触发一次，并在其上使用get请求. API响应后，解析JSON调用将进行模式验证.到目前为止，对于HTTP触发器和Parse JSON，我还不知道禁用JSON验证的方法.我知道当收到HTTP请求时"作为禁用验证选项，但就我而言，不需要当收到HTTP请求时"，我需要基于重复发生的HTTP触发器.

In my Logic app I am using HTTP trigger which fires every 3 hours and using a get request on it. After the API responds, the parse JSON call does schema validation. So far with HTTP trigger and Parse JSON, I don't know a way to disable validation of JSON. I know 'when HTTP request is received' as disable validation option but in my case I don't need 'When http request is recieved', I need HTTP trigger on recurrence basis.

这是我的两个问题 1)使用HTTP触发器时，是否有一种方法可以禁用模式验证，而该触发器会经常重复触发?

Here are my two questions 1) Is there a way to disable schema validation when using HTTP trigger that fires every so often on recurrence basis?

2) 我们对公司进行的API调用，似乎公司经常更新其JSON返回架构.在星期一，呼叫正常进行，在星期二，呼叫没有正确进行.一问他们，这就是他们的回应. 但是几乎所有更改都是添加"，而不是删除"或重新命名"端点和信息.也就是说，这些更改是向后兼容的."

2) The API calls that we make to a company, it seems like the company frequently updates their JSON return schema. On Monday the calls were going through correctly, on Tuesday, they were not. Upon asking them, this is their response. "But almost all changes are "adding", rather than "removing" or "renaming" endpoints and information. I.e. the changes are backward compatible."

我的问题是要添加到架构..验证是否应该在添加后失败，因为逻辑应用程序肯定不会验证其添加，而其代表则听起来像添加"应该向后兼容.架构中的加法会导致验证失败吗?

My question is adding to schema.. is the validation supposed to fail upon addition because logic app for sure is not validating their additions whereas their representative makes it sound like 'adding' should be backwards compatible. Do addition in schema's cause validation to fail?

我正在学习Azure逻辑应用程序，并且不熟悉手边的所有组件. 在方案频繁更改的情况下处理JSON解析的最佳方法是什么，如果可以解决的话如何关闭它.

I am learning Azure logic apps and not familiar with all components at hand. What is the best way to handle JSON parsing in case schema changes frequently and how to turn it off if that is a solution.

推荐答案

在第二个屏幕截图中，似乎与"HTTP触发器"无关.该问题是由解析JSON"(解析组织和组信息)操作中的架构引起的.您需要与公司确认并与他们统一json数据的结构.

In your second screenshot, it seems there is nothing to do with the "HTTP Trigger". The problem is caused by the schema in "Parse JSON"(Parse Organization and Group Information) action. You need to confirm with the company and unify the structure of the json data with them.

在您的第一个屏幕截图中，我认为您需要与公司确认响应json数据中是否包含数组.除此之外，我们可以判断数组是否存在，然后执行选择"操作，如下所示:

In your first screenshot, I think you need to confirm with the company if they have the array in the response json data. Apart from this, we can judge if the array exists and then do the "Select" action, shown as below:

条件"中的fx表达式为:

The fx expression in the "Condition" is:

empty(body('Parse_JSON')?['array'])

希望有帮助〜

这篇关于架构更新验证使Azure逻辑应用程序失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！