General

Re: Versioning and Current Date

BejeweledOne — Wed, 01 Aug 2012 14:44:26 GMT

Sorry to seem obtuse, but when you refer to (my:currentversion) and (my:formloadversion) I am not exactly sure what you mean. I suspect that the 'my:formloadversion' is the version that is retrieved with the substring formula you provided above, but I want to be positive. I am still fairly new to InfoPath and while I am fairly good at setting up rules and such and figuring out the logic behind them, I am not quite up to snuff on all the terms for xpath and such.

Re: Versioning and Current Date

ErnestoM — Wed, 01 Aug 2012 14:26:53 GMT

Sure, here's an attempt. Hope it helps.

Re: Versioning and Current Date

BejeweledOne — Wed, 01 Aug 2012 14:14:17 GMT

Can you give me an example of how to set that up? Thanks

Re: Versioning and Current Date

ErnestoM — Wed, 01 Aug 2012 13:59:18 GMT

That's a good point.

What about storing the version in the main DOM (my:CurrentVersion) and ALSO read in the version from the processing instructions on Form Load (my:FormLoadVersion) and then, if they don't match, run the rule to set the date?

Just an idea - not sure if it will work though! Good luck!

Re: Versioning and Current Date

BejeweledOne — Wed, 01 Aug 2012 13:49:47 GMT

I did this already. I used the set field value to set the date field to 'today()' when the version field changed. Every day it sets the date to the current date even if the version didn't change. This makes me think that when the form is opened it must read the version and 'update' the version field. Pretty sure I indicated in my initial post and the reply that I had already tried this.

Re: Versioning and Current Date

ErnestoM — Wed, 01 Aug 2012 13:12:03 GMT

I'm just guessing... You can set the value of a field to use the version number formula above, then have a rule that sets a date field.

I don't know whether this is exactly what you want, but I'm attaching a sample form that you can look at in design mode.

Good luck!

Re: Versioning and Current Date

BejeweledOne — Tue, 31 Jul 2012 17:23:37 GMT

Sorry if I didn't make myself clear. I have that part down fine. I want to be able to trigger a date field change when the version number changes. I thought I would be able to do that by a simple 'set field value' making the rule to set the date to 'today()' when the version updated. Unfortunately it changes the date everyday. This tells me that the version field must be checked and updated every time you open the form. If you can tell me how to set a date field to the current date (the same date that the version number updates) when the version changes that would be great.

Re: Versioning and Current Date

ErnestoM — Tue, 31 Jul 2012 17:17:02 GMT

You can display the form's version number from the processing instructions by adding an expression box (calculated value) by using this formula:

substring-before(substring-after(/processing-instruction()[local-name(.) = "mso-infoPathSolution"], 'solutionVersion="'), '"')

Hope this helps!

Versioning and Current Date

BejeweledOne — Tue, 31 Jul 2012 14:01:09 GMT

I want to be able to display the current version of the form on the form itself (have this piece in place) and have it update a date box when the version changes. I have tried doing this a couple of ways but the date box always displays today's date regardless if the version has changed or not. In both scenarios Versioning is set to 'Automatically Update'. Not sure this setting would affect what I want to do. The first way was to do a 'set field' action from the version field - Condition: Run when field changes - set date in date field to 'today()'. Second way Hidden date field set to 'today()'. Version field - condition: run when field changes - set date in version date field to = hidden date field. The only conclusion I can draw from this is the version must be read and 'updated' each time the form is opened. I really need this to be in the form and not a promoted field in the SharePoint library. Any help will be greatly appreciated.