title | description | author | manager | editor | services | documentationcenter | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.custom | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Manage integration account artifact metadata - Azure Logic Apps | Microsoft Docs |
Add or retrieve artifact metadata from integration accounts for Azure Logic Apps |
padmavc |
anneta |
logic-apps |
bb7d9432-b697-44db-aa88-bd16ddfad23f |
logic-apps |
integration |
na |
na |
article |
H1Hack27Feb2017 |
11/21/2016 |
LADocs; padmavc |
You can define custom metadata for artifacts in integration accounts and retrieve that metadata during runtime for your logic app. For example, you can specify metadata for artifacts like partners, agreements, schemas, and maps - all store metadata using key-value pairs. Currently, artifacts can't create metadata through UI, but you can use REST APIs to create metadata. To add metadata when you create or select a partner, agreement, or schema in the Azure portal, choose Edit. To retrieve artifact metadata in logic apps, you can use the Integration Account Artifact Lookup feature.
-
Create an integration account.
-
Add an artifact to your integration account, for example, a partner, agreement, or schema.
-
Select the artifact, choose Edit, and enter metadata details.
-
Create a logic app.
-
Create a link from your logic app to your integration account.
-
In Logic App Designer, add a trigger like Request or HTTP to your logic app.
-
Choose Next Step > Add an action. Search for integration so you can find and then select Integration Account - Integration Account Artifact Lookup.
-
Select the Artifact Type, and provide the Artifact Name.
Partner metadata has these routingUrl
details:
-
In your logic app, add your trigger, an Integration Account - Integration Account Artifact Lookup action for your partner, and an HTTP.
-
To retrieve the URI, go to Code View for your logic app. Your logic app definition should look like this example: