InfoPath Dev

SSIA :) I have a site with 2 very similar XML libraries, one of which has at least 1 Query data connection; the other library is the one used for the SharePoint Library Submit DC, but when I try to create a Query DC for it, it cannot get its list of columns ("Encountered an error when retrieving columns: Failed to fetch"). It ...

These are SharePoint lists, and I've used both suggested "hacks" (though I hadn't thought of using the calculated field). Also, I put the concatenation in the Value instead of Display part, particularly when the other fields aren't something to be exposed to the user or the user is only expecting to see one of the fields. ...

Suppose I have a dropdown drawing from a table, and I want the values of 2 different fields for the selection, each being stored in the appropriate form field (for example, the name and code number. I'm guessing I cannot do that directly (although I would love to be proven wrong!). If there were a way to access the other fields of the ...

I added a DropDown element against a dynamic list, but when I try to edit its filter, the control to "Select a field or group..." is disabled. I have other similar DropDowns on the same form whose filters I can edit, EXCEPT for those that do not have a filter specified. Since the ones with filters must have been empty at some point, ...

I'd be happy(-ish) with being able to do it at all.

(Sorry if this is the wrong way to follow-up a question.) For example: * creating HTML label elements associated with various controls? * specifying ALT text for images? * specifying the language for the page?

Are there any tools (native or add-on) to assist with making forms ADA compliant?

There 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.

That 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?

I 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 ...