đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
Can you provide an example use case?
I just tried out mapping an existing Smartbox-based SmartObject to a SQL-based one by remapping the SmartObject from the SmartBox-based services to the SQL-based ones, and didn't see anything break, so I am not sure what you are asking for with this idea.
It's possible to make this kind of change apart from the K2 system:
Copy the SQL object to its new location (rename if you like) and copy data over if it's a table.
Get the GUID of the current SMO
Delete the SMO
Create a new SMO based on the new location of the SQL object, BUT, here's the trick, use the original GUID of the pre-existing SMO.
I've moved tables with thousands of records this way, not just from SmartBox (K2 system DB) but also from other DBs to new DB locations.
Hope this helps!