Search - InfoPath Dev Sign in | Join | Help InfoPath Dev InfoPath Dev is dedicated to bringing you the information and tools you need to be successful in your Microsoft Office InfoPath development projects. Home Blogs Forums Photos Downloads Search More Search Options Page 1 of 2 (18 items) 1 2 Next > Re: Synchronizing SharePoint Task List status with Infopath So I modifed my form to use the SharePoint ID. RefreshSharePointListItems works great except in situations where the task is deleted from SharePoint. In that case, the item is removed from InfoPath as well. I can't have this happen. I'd prefer to have the InfoPath item have it's status changed to "[Associated Task ... Posted to General (Forum) by Tyler Hyland on 03-02-2015 Re: Synchronizing SharePoint Task List status with Infopath It looks like the qRules RefreshSharePointListItems command can do what I need but requires me to use the SharePoint-generated ID instead of the natural key as I had intended. Is my assumption correct? It's not a deal breaker. I'm just trying to stay away from using SharePoint IDs as much as possible to head off any trouble that would ... Posted to General (Forum) by Tyler Hyland on 02-27-2015 Synchronizing SharePoint Task List status with Infopath I've an audit form that contains a repeating group of audit findings. Each finding will be assigned to a user and, upon form submission, a corresponding SharePoint task list item will be created. Rather than relying on the SharePoint ID to link each audit finding with it's corresponding SharePoint task list item, I'm using a natural ... Posted to General (Forum) by Tyler Hyland on 02-27-2015 Re: Mapping InfoPath 2013 person/group picker to SharePoint person/group column using SubmitToSharePointList Perfect! Posted to Qdabra qRules (Forum) by Tyler Hyland on 02-26-2015 Mapping InfoPath 2013 person/group picker to SharePoint person/group column using SubmitToSharePointList As you know, when you add a person/group picker control to an InfoPath 2013 form, a group is created in the main data source. I'm wanting to map this group to a person/group column in a SharePoint task list using SubmitToSharePoint. I followed the instructions outlined here http://goo.gl/dwJXds but the information about repeating group data ... Posted to Qdabra qRules (Forum) by Tyler Hyland on 02-24-2015 Re: Validating fields on submit but not on save That did it. Posted to Controls (Forum) by Tyler Hyland on 02-19-2015 Validating fields on submit but not on save I've prepared an infopath form that will be used for general auditing tasks. The form includes header information (e.g. audit description, audit type, physical location of audit, date, time) and one or more audit findings in a repeating table. The form includes two buttons, a Save button and a Submit button. The Save button allows the user ... Posted to Controls (Forum) by Tyler Hyland on 02-16-2015 Re: Infopath form template functioning as a user interface and as a source for individual instances in a form library I think I may have found something. Let me give this a try. Thanks again for all your help. Posted to General (Forum) by Tyler Hyland on 01-29-2015 Re: Infopath form template functioning as a user interface and as a source for individual instances in a form library The data source for the dropdown is as you suggested. However, the "name" field is not an available field to include. See attached screenshot. Posted to General (Forum) by Tyler Hyland on 01-29-2015 Re: Infopath form template functioning as a user interface and as a source for individual instances in a form library I'm having trouble with step 4. Is there a way that I can query the name of the xml instance after I've selected an employee, perhaps via the value field of the employee selected from the drop down? Ideally, I'd prefer not to blindly assume that an instance follows a particular naming convention. Rather, I'd like to have the ... Posted to General (Forum) by Tyler Hyland on 01-29-2015 Page 1 of 2 (18 items) 1 2 Next > Copyright © 2003-2019 Qdabra Software. All rights reserved.View our Terms of Use.