General

Re: Define current node value based on Secondary ds

Coita Thierry — Mon, 12 Dec 2005 06:42:31 GMT

Ok so I will say to the person that is not possible with this configuration and he has to choose another way!

put a button or put this field in the primary datasource!

Thanks a lot

++

Thierry

Re: Define current node value based on Secondary ds

Matt Faus — Fri, 09 Dec 2005 15:39:32 GMT

Ok, I think I see what you're saying now. I think the problem is not that the field is in the 2DS but that it is not repeating. If you put a non-repeating control inside a repeating control each repetition of the control from the 2DS is simply a copy of the first. If you make a change to any of the 2DS controls the change is reflected in every instance of the repeating section. However, if you change the 2DS control it does not fire a onAfterChange event on the repeating section but only on the 2DS node.

If the 2DS control was repeating you could put it in a group with another field called ID and use the tutorial mentioned above to keep track of which row was being modified.

After playing around a little bit, I think this is impossible within the onAfterChange event of the 2DS field. You'll have to use some kind of trickery like making a field in the repeating section in the primary DS and then copying over to the 2DS and changing every instance manually.

---------------
Matt Faus

Re: Define current node value based on Secondary ds

Coita Thierry — Fri, 09 Dec 2005 06:39:00 GMT

Thanks for your reply Matt! I will explain one more time!

In design mode you have a reapeating section of a primary ds in this you have a field of a secondary ds! This field is always the same in each row of this reapeating section (control cannot repeat here)!

ok ?

On this field of the secondary ds I have a onafterchange event and I want to know which is the current row of the repeating section (primary ds)? the first, the third, the last, ...

With a button in this repeating section it's easy you can make "e.source" and you have the current node! but without in the onafterchange event of the field of the secondary ds is it possible?

I hope that is clear now.

Thierry

Re: Define current node value based on Secondary ds

Matt Faus — Thu, 08 Dec 2005 19:15:06 GMT

quote:
Originally posted by Virgul

With a button it's easy but without? Is it possible?

I'm not sure I understand your question. If it's easy to do with a button, can't you just put the code/rules that you used to do it with a button somewhere else - like in an onAfterChange event? Sorry if I'm misunderstanding.

---------------
Matt Faus

Re: Define current node value based on Secondary ds

Coita Thierry — Thu, 08 Dec 2005 15:00:31 GMT

Hi Matt,

Thanks for your reply! And sorry for my answer but this week I'm sick so I work only when I have the idea clear in my head!

I am a little bit confusing on your answer!If I try to select my current row of my primary datasource with :

IXMLDOMNode test = thisXDocument.DOM.selectSingleNode("/AV/AVel[position()=count(../preceding-sibling::AVel) + 1]")

when I am on a onafterchangeevent from a field of a secondary DS!

This send me always the first row of AVel!

What you would mean in your answer? I don't believe that I have good understand what would you say?

Thanks for your help!

++

Thierry

Re: Define current node value based on Secondary ds

Matt Faus — Fri, 02 Dec 2005 15:08:30 GMT

I used this tutorial when doing something similiar - it helped a lot!
http://www.infopathdev.com/howto/tutorials/default.aspx?i=d663d7df90e94e65abb02632966e8127

Using the index that you create with that tutorial it should be easy to reference which repeating section you're currently on, and then reference the nodes within this repeating section to make appropriate changes.

---------------
Matt Faus

Define current node value based on Secondary ds

Coita Thierry — Fri, 02 Dec 2005 08:45:00 GMT

Hi,

Somebody has asking me a question that I can solve here it is:

You have in a primary ds a reapeating choice section and in this you have two fields from a secondary datasource and other from primary!

And with a onafter change event or a rules based on this field of secondary DS you need to populate the current reapeating choice section of the primary DS!

How you make?

With a button it's easy but without? Is it possible?

Thanks from this user

Thierry