https://www.infopathdev.com:443/forums/190.aspxView and edit existing forms without InfoPath - includes most qRules functionality!enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/125682.aspxTue, 28 Oct 2025 15:52:48 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125682Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/125682.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125682Oh cool. So in InfoPath designer, we had the option to "demote" a property which would make it writable in the library. We do not have that in FormsDesigner yet, so changing read-only on the field is a great idea.https://www.infopathdev.com:443/forums/thread/125681.aspxTue, 28 Oct 2025 15:42:24 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125681sbhunter0https://www.infopathdev.com:443/forums/thread/125681.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125681There is a PATCH HTTP call to SharePoint that sets the ReadOnly-ness of a specified field; this was enough not only to be able to edit properties of the field, but also make it accessible for update via Power Automate. Not the most straight-forward solution, but I've endured much nastier work-arounds.https://www.infopathdev.com:443/forums/thread/125680.aspxTue, 28 Oct 2025 13:54:09 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125680sbhunter0https://www.infopathdev.com:443/forums/thread/125680.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125680That was very helpful (that may sound sarcastic, but it absolutely is not), but leads to a follow up: Fields that were added to the library by FormsViewer (via promoted properties) are readable from a Power Automate flow, but don't show up in the list of fields that can be updated. Is there a way to address this?https://www.infopathdev.com:443/forums/thread/125678.aspxThu, 23 Oct 2025 18:44:41 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125678Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/125678.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125678Are you using FormsDesigner for this? Or InfoPath? I would use a promoted property for this. The field gets added to the form first. Then, in InfoPath, if you walk through the publishing wizard (i.e., don't use quick publish) you have the opportunity to add the new field as a promoted property in your library. If you are using FormsViewer, you can add your form fields as promoted properties and modify the form publish location under the "publish" tab. Please let me know if you need additional information! EDITED TO ADD: I see now this is in the FormsViewer forum, so I'll assume you are using FormsViewer :-) Feel free to reach out if you want to schedule a call for a quick walk-through!https://www.infopathdev.com:443/forums/thread/125676.aspxThu, 23 Oct 2025 16:20:59 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125676sbhunter0https://www.infopathdev.com:443/forums/thread/125676.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125676I have an XML Library & a form defined for it. I want to add a field to that form and have it show up as a column in the XML library that it posts to. What is the proper sequence of adding it to the form, the library, and the list of promoted properties (or what to use instead of promoted properties) so that the submitted value is displayed in both the form & in the library (and, presumably, be available to access from a Power Automate flow)?