In Nintex for SharePoint On-Prem versions, there was a Form SQL Request control. This control allowed you to query a table or view, and to Execute a SQL query, or run a stored procedure. If you selected a Query type of SQL, you were presented with a place to write your own SQL query.

In NWC, when creating a data source, there is no option to execute a SQL query or stored procedure.

For the NWC form designer, there is no control that allows you to Write or Execute a SQL query.

And in the NWC workflow designer, none of the MS SQL Server On-Prem controls allow you to write a SQL query.

The Execute a Query control is not available in SQL Server On-Prem,

On both the NWC form designer and the workflow designer, it would be beneficial to have the ability to write executable SQL code, that allows us to use Aliases, Joins (Inner, Outer, Left, Right, Self), Union, Group by, Order by, Having, Count, Min, Max, Sum, Wildcards, Select Distinct, etc.

Currently only the workflow MS SQL Server > Execute a query control has that ability. Can that functionality be added to the On-Prem SQL controls, and/or to a Form control, or Data Source?

Not a product problem. But something that has popped up a few times now when dealing with Salesforce Leads. Having the ability to convert a lead to a contact and be able to configure an action to create a new account / Opportunity or assign . the lead to Account / Opportunity IDs would be be really great.
The only way to achieve this at the moment, with out using APEX is to look for a lead, and if it existing copy all the information to variables. Delete the lead and the recreate a new contact using the stored data in the variables..

Here is the process if you were to build it in Process Builder. https://automationchampion.com/tag/auto-convert-lead-using-process-builder

The forms designer we're leaving in favor of NWC allows for fields to be different sizes, independent of the accompanying text. I wish NWC would allow this. For example, I might have a Text - Short field with a long title but the expected user input is only a few characters. If I make the field as small as possible, the text wraps to match the field size. If I try to prevent the text wrapping, the field expands to be just as long. It would be nice if you could have a long title, with no wrapping, but still have a small input field.

I've come across a use case in which it would be helpful if checking a box in one choice field would uncheck a box in a previous choice field. In other words, clicking the box in the second field invalidates the checked box in the first.

Also, I haven't come across such a need myself, but I could also see the need for the ability to hide or "gray out" certain options in a multi-choice field based on one of the other options being selected. For example, if my options were 1,2,3,4,5 and the user selects 3, the 4 and 5 options are then removed because they no longer apply or whatever.

In other words, rules for choice fields ...

I feel like you should be able to leverage the form component "people" drop down even if the form is not set up for only Authenticated Users in this Tenant. My request is to allow for an Anonymous form with Anyone with this form Url link should be able to somehow leverage a drop down of people in our org. OR in order to solve a different problem, make it easier to add everyone from your O365 tenant into Nintex Workflow Cloud users, instead of only being able to add 1 by 1. Often times I'm building applications that anyone in our org needs to complete a form and I'm not going to sit here for hours adding 1000 users to Nintex Workflow cloud.

When using the Add a Row or Update a Row actions, the only available cells to change are the ones that are visible within SmartSheet. Hidden columns are not available within NWC to use. We have some situations where there may be hidden columns (columns the SS user doesn't need to see), that we need to update via NWC. Currently, we can't do this since NWC doesn't populate those columns.

As an example, I have a SmartSheet grid that has a column for the Workflow Instance ID of the workflow that added/updated the row of the sheet. The end user doesn't need to see this information, so I have the column hidden to not clog up there workspace. Once that column is hidden, it no longer shows up with NWC's Add/Update a Row actions.

This leads to very confusing results when columns are hidden AFTER a workflow action has been configured. The action may be configured to set a column value, but if you click on the action it won't show because the column is hidden - leading you to assume the action isn't doing something when it actually is.

Please allow the Add/Update a Row actions to display all cells, not just the visible ones.