Qdabra qRules

Re: Mapping xmls contains GUID

Hilary Stoupa — Tue, 05 Jun 2012 14:50:49 GMT

I think there may be a work around ... I was about to tell you that due to the way qRules currently functions, you'll need to change the GUIDs, but on second thought, that may not be needed.

You should be able to just change the GUID in the mapping List Collection node to the list name. I just tested this in filler and browser, and it worked correctly. You'll need to change your mapping files manually in a text editor (or via rules in your form) - but you only need to make the change one time.

I do have furture plans to make this possible through the mapping tool - but those are going to be coming in about 4.3 or 4.4.

Re: Mapping xmls contains GUID

SENTHIL KUMAR G — Tue, 05 Jun 2012 04:36:20 GMT

Hi Hillary,

Currently we are using the same SharePoint URL and all the custom lists will have the same name in all the environment.

Our scenario is we map the info path using qRules to 1 form library and 3 custom lists where data's are getting saved properly to the library and lists. No issues on this.

When we move the newly created info path form using qRules (which contains 40+ mapping xml file) to the test environment it doesn't work because the 40+ mapping xml files will have the development environment custom lists GUID. In the test environment the GUID will be different for custom lists.

So we need to change the GUID in the mapping file manually for all the 40+ xml with the new GUID of the custom lists in the test environment.

This will be a continuous process when we move this to acceptance/production environment.

Hope I am clear with the scenario this time which could help you to provide a better solution through qRules.

Thanks

Senthil Kumar

Re: Mapping xmls contains GUID

Hilary Stoupa — Mon, 04 Jun 2012 15:15:24 GMT

Hi - do your different environments also use a different SharePoint URL? Or is it just the GUID that is the issue? Do all the lists have the same name? Are you mapping your form to 40 lists? (You mention 40 mapping XML files, so I don't quite understand your scenario).

If the issue is that the form is deployed to different SharePoint sites where the list may have a different GUID but the same schema, one option may be to keep a list with the GUIDs and the library the form is deployed to and then use form logic to set the GUID when it is opened.

Mapping xmls contains GUID

SENTHIL KUMAR G — Mon, 04 Jun 2012 13:19:20 GMT

While creating a mapping using qRules, list’s Guid is added in to the xml mapping file. So when you move the info path form from one environment to another it doesn’t work; as it is pointing to the old list guid. If we change manually it works fine which is not advisable because we have around 40+ mapping xml files. This is just an work around.

Is there any alternate way for xml mapping so that we need not change the GUID?