Search results for '12'

Re: Datepicker Placement weirdness

Jimmy — Wed, 21 Oct 2026 01:44:09 GMT

Hello, Very sorry for our delay in replying to this thread. Just to follow up on it - you contacted us by e-mail about this the day after posting here and Sweta replied with a likely solution. Please let us know in that e-mail thread if you still need any assistance. Thank you!

Datepicker Placement weirdness

sbhunter — Tue, 01 Sep 2026 19:59:34 GMT

I have a long (more than a screenful) FV form w/ multiple date fields. When clicking on each's datepicker icon, a datepicker dutifully appears, but only for the topmost one is it located anywhere near the associated field. There isn't much in the way of styling or JS that doesn't come from Qdabra, but are there things I should be looking for that might be causing this?

Re: Cannot create a Query Data Connection for one Library of a site, but can for very similar ones on same site

Patrick Halstead — Mon, 27 Jul 2026 16:55:03 GMT

Hi Scott,

Sorry for the delay. Short version: the CORS error is a symptom, not the problem. The real signal is that our WebProxy handed your browser a redirect to the Entra sign in page, and a fetch() call cannot follow that across origins, so Chrome reports it as a CORS failure with that odd "ERR_FAILED 200 (OK)". Nothing is misconfigured about CORS, and there is nothing to fix at login.microsoftonline.com.

One thing worth stating clearly: SharePoint Online does not redirect REST calls to the authorize endpoint. If the account simply lacked rights on that library, the call would come back as a clean 401 or 403. A redirect to /authorize means FormsViewer could not silently obtain a token for that call and tried to start an interactive sign in. So this is token acquisition, most likely one of:

The two libraries are not actually in the same site collection, and the token we hold is scoped to the other one.
The token or session expired between your two attempts.
A Conditional Access policy or a pending consent applies to that site and forces interactive re-auth.

Three things would let us pin this down quickly:

The full, unredacted authorize URL from the console. The query string usually names the cause directly. Look for error, error_description, prompt, client_id, and scope or resource. Scrub anything you consider sensitive, but the parameter names matter.
The two GetColumnsByListId request URLs side by side, the working library and the failing one, so we can compare the web URL and list ID parameters.
The FormsViewer server log entries from that moment, so we can see what SharePoint actually returned before we issued the redirect.

A quick test that splits the problem in half. Signed in as the same user, browse to:

{site}/_api/web/lists(guid'{list id}')/fields?$select=InternalName,Title

If that returns data, the library permissions are fine and this is our token handling. If it returns 403, it is a permissions issue after all and we look at that library's unique permissions.

Also worth one minute: sign out and back in, then configure the failing library first, before touching the other one. If it works, it was a stale token.

On a workaround, you can copy the working Query data connection and repoint it at the other library's list ID and URL, which bypasses the Designer's column picker. Two cautions. The internal column names have to match exactly or the form binds to nodes that do not exist and fails at runtime, and if the runtime query goes through the same WebProxy path it may hit the same auth problem on form load. Test it end to end rather than in preview.

What FormsViewer version are you running? We have made a number of changes recently and I want to be sure we test against your build.

Re: Problem w/ User Display

Patrick Halstead — Mon, 27 Jul 2026 14:34:13 GMT

Hi SB and sorry for the delay in responding. Can you send an image of the issue to support@qdabra.com (no fee) and we'll investigate. We have been making a lot of changes to FormsViewer and FormsDesigner recently, and it's possible that it is a regression. Are you using online or on premium version? need more details

Problem w/ User Display

sbhunter — Mon, 13 Jul 2026 12:56:18 GMT

I have an old (year or so) FV form which displays users in a number of places. Normally, the user's name is shown in a box w/ an X for removing it. However, now the name is no longer shown, although the box & the X are still there. And if I look at the underlying HTML, I can see an attribute w/ the user's email address. The same data, when displayed using the InfoPath form that the FV form was derived from, does not have this issue. And a new version of the FV form does not seem to, either. (We need the "old" FV version to display old data), the new FV form will be working off a different slightly modified library.) Has anyone seen this and, better, know how to address it?

Cannot create a Query Data Connection for one Library of a site, but can for very similar ones on same site

sbhunter — Fri, 22 May 2026 19:00:39 GMT

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 seems be running afoul of CORS:

Access to fetch at 'https://login.microsoftonline.com/3456fe92-cbd1-406d-b5a3-5364bec0a833/oauth2/v2.0/authorize?...' (redirected from 'https://formsv.nycourts.gov/WebProxy/GetColumnsByListId?...')
     from origin 'https://formsv.nycourts.gov' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
middleware.js:18  GET https://login.microsoftonline.com/3456fe92-cbd1-406d-b5a3-5364bec0a833/oauth2/v2.0/authorize?...  net::ERR_FAILED 200 (OK)

What can I do to query this library?

2025 Qdabra Forms Master Class

Hilary Stoupa — Tue, 28 Apr 2026 20:11:58 GMT

Access video recordings and lab materials from the 2025 Qdabra Forms Master Class here - includes everything you need for your own, on-demand Qdabra Forms Training.

Workaround for deprecated GetUserProfileByName web service method

Hilary Stoupa — Thu, 26 Feb 2026 21:34:00 GMT

If you are using Qdabra Forms and SharePoint Online, you may have run into this issue - the old UserProfileService.asmx service has been deprecated! This means we can't create a data connection for that service any longer. The qRules Command "GetUserProfileByName" doesn't rely on the web service for data, but it does need a data source to put the user data in.

One option is to use one of the XTPs we have provided here. The XTP already has logic set up you can easily leverage, and will add the needed data connection to your form.

You can also just use the XML from a previously created GetUserProfileByName data connection - I've uploaded a copy here. Just download the file, and add it to your form as a resource file. Create an XML data connection to the resource file - be sure to set it to query on load. I name mine "GetUserProfileByName" so I don't have to pass the data source name into the command.

Re: Multi-field Dropdown Value

sbhunter — Thu, 29 Jan 2026 13:12:01 GMT

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. Looking forward to your proposed feature!

Re: Multi-field Dropdown Value

Hilary Stoupa — Tue, 27 Jan 2026 21:13:24 GMT

I think you will need a display value that combines these - when you say "from a table" do you mean a SQL table? If so, I'd use a SQL view to create the concatenated name and code number. Then I'd use that for my dropdown. I'd add rules to set the individual fields to the correct data when the dropdown value is selected. So, my view might have Display (the concat), Code, Name. When the Display is selected, I use rules to set the form fields to the Code and the Name. If this is a SharePoint list, I'd use a calculated field for the concat... It may be possible to manually manipulate the view file to use the combined fields for the display, but I would generally not recommend that - because that is notoriously fragile..... I'm going to open a proposed future feature for FormsDesigner to allow using a formula for the display / value properties for a dropdown, however. We are starting to gather and implement ideas that move Qdabra Forms beyond what was possible in InfoPath and I think this is worth consideration.