Data Connections

Re: Current and Position ---- always one (1) ?

Maureen57 — Wed, 02 Feb 2011 19:49:57 GMT

Can you use an index or a relative path when you call an email webservice?

I seem to always be feed the email with the first instance of the group.

Re: Current and Position ---- always one (1) ?

Maureen57 — Wed, 19 Jan 2011 16:11:08 GMT

Worked again...THANK YOU so much

Re: Current and Position ---- always one (1) ?

Jimmy — Wed, 19 Jan 2011 15:32:10 GMT

Try removing the ../

Re: Current and Position ---- always one (1) ?

Maureen57 — Wed, 19 Jan 2011 15:14:22 GMT

Trying to use relative paths --- following some instructions I found on this site. This is my code:

XDocument.DataObjects("vw_Fedex_SPOD_N").DOM.setProperty("SelectionNamespaces",'xmlns:dfs="http://schemas.microsoft.com/office/infopath/2003/dataFormSolution"xmlns:d="http://schemas.microsoft.com/office/infopath/2003/ado/dataFields" ');

trackingnum = eventObj.Source.selectSingleNode("../@TransmartTrackingNumber").text;

With this syntax, I get the error that there is no object.

THANK YOU THANK YOU

Re: Current and Position ---- always one (1) ?

Jimmy — Wed, 19 Jan 2011 04:32:44 GMT

The reason Source isn't doing what you expect is that you're using absolute XPaths. You need to use relative XPaths.

Re: Current and Position ---- always one (1) ?

Maureen57 — Wed, 19 Jan 2011 03:23:13 GMT

The reason I needed to find the current member of the group is because when I used this statement in the button code, it always pulled the first instance of d:vw_Fedex_SPOD_N

trackingnum = eventObj.Source.selectsingleNode("/dfs:myFields/dfs:dataFields/d:vw_Fedex_SPOD_N/@TrackingNumber").text;

(Not sure why that didn't get the current instance. Everything I read said it would....)

Now (thanks to you), I have a number on the form that evaluates correctly to the current instance index. The index variable is instance_nbr, and it does evaluate correctly to the current instance of d:vw_Fedex_SPOD_N in the button code.

var nodesDetail = XDocument.DOM.selectNodes("/dfs:myFields/dfs:dataFields/d:vw_Fedex_SPOD_N");

var row = nodesDetail.item(instance_nbr);

trackingnum = row.selectSingleNode("@TrackingNumber").text

But the last statement throws an error - null is null or not an object.

How can I use this index to load the correct instance values into fields?

THANK YOU

Re: Current and Position ---- always one (1) ?

Maureen57 — Tue, 18 Jan 2011 18:46:03 GMT

THANK YOU!

Re: Current and Position ---- always one (1) ?

Maureen57 — Tue, 18 Jan 2011 18:45:07 GMT

It worked ---- !!!!!!! Thank you thank you.

Re: Current and Position ---- always one (1) ?

Jimmy — Tue, 18 Jan 2011 18:28:13 GMT

Your button rule is setting the field to the string value "count(preceding-sibling::vw_Fedex_SPOD_N)". You need to use the formula editor dialog. I was mistaken in the formula I gave. It should be:

count(preceding-sibling::d:vw_Fedex_SPOD_N) + 1

The reason the field is always showing 1 is that you have a rule on the field that sets itself to the value of count(.) (which is always 1) when its value is modified. You need to disable that rule.

Re: Current and Position ---- always one (1) ?

Maureen57 — Tue, 18 Jan 2011 18:15:22 GMT

Here it comes --- the DUMMY button is the one with the new rule, setting the ID field to count(preceding-sibling::vw_Fedex_SPOD_N)

Re: Current and Position ---- always one (1) ?

Jimmy — Tue, 18 Jan 2011 17:38:47 GMT

Could you post your form here again with those modifications?

Re: Current and Position ---- always one (1) ?

Maureen57 — Tue, 18 Jan 2011 16:50:55 GMT

Many thanks for your help ---

I created a button inside my repeating section, added one rule - to set a fields value to count(preceding-sibling::vw_Fedex_SPOD_N)

Then, I previewed the form. There were three instances of the repeating section.

I clicked the button in instance 1 - field value set to 1.

I clicked the button in instance 2 - field value set to 1.

I clicked the button in instance 3 - field value set to 1.

What am I doing wrong? How do I get the current instance number?

Re: Current and Position ---- always one (1) ?

Maureen57 — Mon, 17 Jan 2011 13:57:07 GMT

Thank you, will try....

Re: Current and Position ---- always one (1) ?

Jimmy — Mon, 17 Jan 2011 13:44:21 GMT

position() and current() just don't work like that.

You should be able to use this formula in your button's rule to determine the row number where that button was clicked.

count(preceding-sibling::vw_Fedex_SPOD_N)

Re: Current and Position ---- always one (1) ?

leoffneym — Mon, 17 Jan 2011 13:44:04 GMT

By "Current" do you actually mean where the cursor is, or the last row of the repeating table.

If you mean the last row of the repeating table, you have to use the 'last()' command in the x-path.

Ex: /my:myFields/my:NameOfGroup/my:NameOfRepeatingTable[last()]/my:NameOfField

Name	Number
Item 1	1
Item 2	2
Item 3	3

To get the last of Number from this table, it would be: /my:myFields/my:Group1/my:ItemTable[last()]/my:Number

The my namespace, myFields and Group1 can be different depending on you setup your fields.

If you are trying to get the true current(where the cursor is) value, I don't think it possible.

GMoore