Expand my Community achievements bar.

SOLVED

Binded fields associated with separate Web Service requests

Avatar

Level 2

Hi,

I'm attempting to create a Data Connection that allows the user to select from approximately 2000 attributes. Presently, my web service operation request takes in an ID value and returns an object encapsulating these 2000 attributes.
If for example I have a "firstName" attribute is it possible to have 2 instances of this field on my form but associated with different request IDs?
If so, how do I go about this?

Thanks.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I assume that the workitemID is unique for eachweb servce call made ...correct. So in fact you are making two different web service calls and want to bind the name to the same field but maintain the data from the previous call right?

Paul

View solution in original post

21 Replies

Avatar

Former Community Member

Bottom line is that if you return a string of XML from your web service (instead of distinct individual parameters), you can load the xml into the client data dom and place it into the fields you want programatically. This gives you better flexibility and control.

Paul

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----