S.Y.M. Wong-A-Ton - Need your Help :)

[Art]

I have a great form I am developing in IP 2003.

Based on a person's email, it retreives a travel profile from a SQL table.

I use the following default value to populate the individual fields:

..../../dfs:dataFields/d:tblTravelProfile/@FirstName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email = ../@EMail]

All that gets changed is the name of the field in the Travelprofile such as

..../../dfs:dataFields/d:tblTravelProfile/@LastName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email = ../@EMail]


What I am experiencing is an inconsistent return of data. The first field
on the form always returns the correct data but the remaining fields
sometimes return data and sometimes they don't.

I even added a NOLOCK clause to the SQL statement just in case the table was
getting locked during data retreival and that did not good.

There are no special characters in the data.

Any idea on where to point me to troubleshoot?

 

[S.Y.M. Wong-A-Ton]

Are you using the default value on fields in a repeating table or section?

 

[Art]

Even though it is pulling data, I know so there will always only be a
one-for-one match so it is not a repeating table or section

Are you using the default value on fields in a repeating table or section?
---
S.Y.M. Wong-A-Ton

I have a great form I am developing in IP 2003.

Based on a person's email, it retreives a travel profile from a SQL
table.

I use the following default value to populate the individual fields:

../../dfs:dataFields/d:tblTravelProfile/@FirstName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]

All that gets changed is the name of the field in the Travelprofile such
as

../../dfs:dataFields/d:tblTravelProfile/@LastName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]


What I am experiencing is an inconsistent return of data. The first
field
on the form always returns the correct data but the remaining fields
sometimes return data and sometimes they don't.

I even added a NOLOCK clause to the SQL statement just in case the table
was
getting locked during data retreival and that did not good.

There are no special characters in the data.

Any idea on where to point me to troubleshoot?

 

[S.Y.M. Wong-A-Ton]

Have you made any progress with this? If not, could you please explain a bit
more how you created your form? I can see that you are retrieving data from
the Main data source (probably your form is bound to a database?) and that
you are filtering on a secondary data source that is getting its data from a
web service? And also, have you tried using rules instead of setting the
default value? It is unlikely that SQL Server is causing the issue; the first
place I would look for a problem is in InfoPath.
---
S.Y.M. Wong-A-Ton

Even though it is pulling data, I know so there will always only be a
one-for-one match so it is not a repeating table or section

Are you using the default value on fields in a repeating table or section?
---
S.Y.M. Wong-A-Ton

I have a great form I am developing in IP 2003.

Based on a person's email, it retreives a travel profile from a SQL
table.

I use the following default value to populate the individual fields:

../../dfs:dataFields/d:tblTravelProfile/@FirstName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]

All that gets changed is the name of the field in the Travelprofile such
as

../../dfs:dataFields/d:tblTravelProfile/@LastName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]


What I am experiencing is an inconsistent return of data. The first
field
on the form always returns the correct data but the remaining fields
sometimes return data and sometimes they don't.

I even added a NOLOCK clause to the SQL statement just in case the table
was
getting locked during data retreival and that did not good.

There are no special characters in the data.

Any idea on where to point me to troubleshoot?

 

[Art]

I got it to work but by taking a totally different approach

Rather than having the query file off automatically based on rules on a
field obtained from the web service, I redid the form to call the data from
the web service on load and then have the user click on a query button to
retrieve their travel profile.

I suspect there is some obscure bug somewhere but taking the different
approach, all I have addred is one click by the user.

Is there a way to autofire the query rather than have the users click a
button?

Have you made any progress with this? If not, could you please explain a bit
more how you created your form? I can see that you are retrieving data from
the Main data source (probably your form is bound to a database?) and that
you are filtering on a secondary data source that is getting its data from a
web service? And also, have you tried using rules instead of setting the
default value? It is unlikely that SQL Server is causing the issue; the first
place I would look for a problem is in InfoPath.
---
S.Y.M. Wong-A-Ton

Even though it is pulling data, I know so there will always only be a
one-for-one match so it is not a repeating table or section

Are you using the default value on fields in a repeating table or section?
---
S.Y.M. Wong-A-Ton


:

I have a great form I am developing in IP 2003.

Based on a person's email, it retreives a travel profile from a SQL
table.

I use the following default value to populate the individual fields:

../../dfs:dataFields/d:tblTravelProfile/@FirstName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]

All that gets changed is the name of the field in the Travelprofile such
as

../../dfs:dataFields/d:tblTravelProfile/@LastName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]


What I am experiencing is an inconsistent return of data. The first
field
on the form always returns the correct data but the remaining fields
sometimes return data and sometimes they don't.

I even added a NOLOCK clause to the SQL statement just in case the table
was
getting locked during data retreival and that did not good.

There are no special characters in the data.

Any idea on where to point me to troubleshoot?

 

[S.Y.M. Wong-A-Ton]

Did you already try using a rule with an action of "Query using a data
connection"?
---
S.Y.M. Wong-A-Ton

I got it to work but by taking a totally different approach

Rather than having the query file off automatically based on rules on a
field obtained from the web service, I redid the form to call the data from
the web service on load and then have the user click on a query button to
retrieve their travel profile.

I suspect there is some obscure bug somewhere but taking the different
approach, all I have addred is one click by the user.

Is there a way to autofire the query rather than have the users click a
button?

Have you made any progress with this? If not, could you please explain a bit
more how you created your form? I can see that you are retrieving data from
the Main data source (probably your form is bound to a database?) and that
you are filtering on a secondary data source that is getting its data from a
web service? And also, have you tried using rules instead of setting the
default value? It is unlikely that SQL Server is causing the issue; the first
place I would look for a problem is in InfoPath.
---
S.Y.M. Wong-A-Ton

Even though it is pulling data, I know so there will always only be a
one-for-one match so it is not a repeating table or section


Are you using the default value on fields in a repeating table or section?
---
S.Y.M. Wong-A-Ton


:

I have a great form I am developing in IP 2003.

Based on a person's email, it retreives a travel profile from a SQL
table.

I use the following default value to populate the individual fields:

../../dfs:dataFields/d:tblTravelProfile/@FirstName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]

All that gets changed is the name of the field in the Travelprofile such
as

../../dfs:dataFields/d:tblTravelProfile/@LastName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]


What I am experiencing is an inconsistent return of data. The first
field
on the form always returns the correct data but the remaining fields
sometimes return data and sometimes they don't.

I even added a NOLOCK clause to the SQL statement just in case the table
was
getting locked during data retreival and that did not good.

There are no special characters in the data.

Any idea on where to point me to troubleshoot?

 

[Art]

Yes

Both before the rule setting the values and after and even both before and
after the rules

I suspect it is a bug in IP 2003.

Did you already try using a rule with an action of "Query using a data
connection"?
---
S.Y.M. Wong-A-Ton

I got it to work but by taking a totally different approach

Rather than having the query file off automatically based on rules on a
field obtained from the web service, I redid the form to call the data from
the web service on load and then have the user click on a query button to
retrieve their travel profile.

I suspect there is some obscure bug somewhere but taking the different
approach, all I have addred is one click by the user.

Is there a way to autofire the query rather than have the users click a
button?

Have you made any progress with this? If not, could you please explain a bit
more how you created your form? I can see that you are retrieving data from
the Main data source (probably your form is bound to a database?) and that
you are filtering on a secondary data source that is getting its data from a
web service? And also, have you tried using rules instead of setting the
default value? It is unlikely that SQL Server is causing the issue; the first
place I would look for a problem is in InfoPath.
---
S.Y.M. Wong-A-Ton


:

Even though it is pulling data, I know so there will always only be a
one-for-one match so it is not a repeating table or section


Are you using the default value on fields in a repeating table or section?
---
S.Y.M. Wong-A-Ton


:

I have a great form I am developing in IP 2003.

Based on a person's email, it retreives a travel profile from a SQL
table.

I use the following default value to populate the individual fields:

../../dfs:dataFields/d:tblTravelProfile/@FirstName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]

All that gets changed is the name of the field in the Travelprofile such
as

../../dfs:dataFields/d:tblTravelProfile/@LastName[xdXDocument:GetDOM("GetUserProperties")/dfs:myFields/dfs:dataFields/tns:GetUserPropertiesResponse/tns:GetUserPropertiesResult/tns:Email
= ../@EMail]


What I am experiencing is an inconsistent return of data. The first
field
on the form always returns the correct data but the remaining fields
sometimes return data and sometimes they don't.

I even added a NOLOCK clause to the SQL statement just in case the table
was
getting locked during data retreival and that did not good.

There are no special characters in the data.

Any idea on where to point me to troubleshoot?