Data Connections

Re: Trouble with "Convert Main Data Source"

Shiraz Cupala — Mon, 22 Jan 2007 20:53:46 GMT

The Convert Main Data Source algorithm is very intelligent but not perfect. It could also just be an issue of hitting a limitation. If what Shalaja says isn't the issue for you then you should be able to just right-click and fix the binding manually.

Re: Trouble with "Convert Main Data Source"

shailaja — Tue, 31 Oct 2006 16:54:14 GMT

Hello Brain,
The reason for the controls becomeing unbound are two: First if the Control name in the old schema does not match the control name of new schema, secondly if the control is present in old schema but in new schema
I have a small example First I had my schema as follows
<Test>
<ID></ID>
<Name></Name>
<Class></Class>
</Test>
Now I tried upload an xml using "Convert Main Data Source" by adding new root element to the schema. It looks as follows
<Tests>
<Test>
<Id></Id>
<Name></Name>
<Address></Address>
</Test>
</Tests>
After doing this I got two controls unbound. one is ID as it was declared as "ID" in old schema and changed to "Id" in new schema, second is Class which was present in old schema but not in new schema

Hope this helps!

Trouble with "Convert Main Data Source"

faivre — Mon, 16 Oct 2006 20:17:41 GMT

Hello,

I am having trouble using the "Convert Main Data Source" functionality of InfoPath 2003 SP2. I want to add a new root element in my schema. When I do this about 1/3 of my controls become unbound. I can't see any pattern with the controls that are bound correctly vs the ones that are unbound.

Any ideas?

Thanks,

Brian