查找值 [英] Lookup Values

问题描述

大家好， 

我正在寻找替代解决方案，为多个逻辑应用工作流程提供转换查找值。我过去曾在SSIS工作流程中使用过SQL数据库这些类型的查找，但只是想知道是否有其他人使用过
其他内容，例如Azure存储或集成地图（例如Liquid）等。

我所拥有的一个示例场景是生成JSON文件的上游系统，该文件在有效负载中具有3个字符的ISO国家代码。有几个工作流程可以使用此有效负载，一个将代码转换为2个字符的代码，而另一个LA将代码转换为b $ b代码到国家名称。 

如上所述我想过使用一个数据库，当需要新的查找转换时，我要么添加一个新的查找表，要么使用一个键值或EAV结构来为转换提供服务。这已经感觉它不能很好地扩展为
我会向LA添加额外的操作，因为需要更多的转换或者最终编写一些Funky SQL Stored Proc来试图容纳。如果查找映射是一个小集合，使用
一个案例控制流程或类似情况，每个工作流程/ LA的液体变换看起来都很合适。但对于像ISO国家代码这样的大型映射，可维护性会很痛苦。我还想过为这些边缘情况使用公共ISO国家/地区代码API，但希望限制必须在LA
工作流程中添加其他操作。  

谢谢

解决方案

我相信使用Azure功能进行所有这些处理非常合适你可以

从您的逻辑应用程序调用。

您的函数可以从您的数据库或API获取所需的查找（甚至可以通过简单地将其存储在静态变量中来将其缓存在函数调用中）它可用于对JSON有效负载执行必要的更改并返回转换后的JSON。

这将只占逻辑应用程序中的单个操作，并将所有复杂处理卸载到函数中

Hi All, 

I am looking for alternative solutions for providing transformation lookup values for several logic app workflows. I have used a SQL database in the past for these type of Lookups in SSIS workflows but was just wondering if anyone else had used something else such as Azure Storage or Integration Maps (e.g. Liquid) etc.

An example scenario I have would be an upstream system generating a JSON file which has a 3 character ISO Country Code in the payload. Several workflows could use this payload, one transforms the Code to a 2 character code while another LA would transform the code to the name of the country. 

As mentioned above I thought of using a database where as a new lookup transformation is required I would either add a new lookup table or use a key value or EAV structure to service the transformation. This already feels like it would not scale well as I would add additional actions to the LA as more transformations are required or end up writing some Funky SQL Stored Proc to try to accommodate. A liquid transform for each workflow/LA looks like it would fit if the lookup mappings were a small set using a case control flow or similar. But for larger mappings like ISO Country Codes maintainability would be a pain. I have also thought of using a public ISO Country Code API for these edge cases but wanted to limit having to adding additional action to the LA workflow.  

Thanks

解决方案

I believe using an Azure Function for all this processing would be a great fit which you can call from your Logic App.

Your function could fetch the required lookup from your DB or an API (and even cache it across function calls by simply storing it in a static variable) which it can use to perform the necessary changes to the JSON payload and return the transformed JSON.

This would account for just a single action in your Logic App with all of the complex processing offloaded to the function.

这篇关于查找值的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！