StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1440932
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-09-17T19:41:24.587
FavoriteCount
0
LastActivityDate
2009-09-17T19:41:24.587
LastEditDate
LastEditorUserId
0
OwnerUserId
107330
ParentId
1401249
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The approach you suggest, where you do the transform and then use a .NET assembly to replace IDs with descriptions, should work for relatively small messages but you'll have problems with larger messages. Another option is to create a multi-part message that contains your original type, plus a new type. The new type is one you create that you load with the name-value pairs before you transform. So you now have two messages - Y (your message) and X (the message that contains the name-value pairs). Take a copy of your existing map in case it breaks, then modify the transform shape so that it accepts both types (type Y and type X) - the order is not important. In your map - at the places where you need to perform the lookup, add a scripting functoid and set it to Inline XSLT. In the inline XSLT add your node name, followed by an xsl:value-of select... element. Put an xpath expression into the select statement that looks up the ID and selects the value. A simple expression could be something like /Root/Lookups[@id="12345"]/ - but of course your expression will be different. You can get an idea of how to address the message part by clicking the node that holds the name-value pairs and select the Instance XPath in the properties filed. It's going to take some practice if you are not familiar with XPath or namespaces, etc - but when it works, it will be fast and will work seamlessly, and you'll have less code to maintain.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAlternative to running DB Lookup functoid through a loop?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USErik Westermann
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.