Hi everyone, I have been testing my form and only can i see the content populate from the database in the testing enviornment and not in the LIVE. Can anyone please tell me what is wrong? Why is this only populating in TEST MODE only?
SQL Query works only in testing enviornment not in LIVE...
+3
+5Starting from square one... did you update the server/database names to your live SharePoint environment?
+5Does the production database use a different authentication? Does the table have a different column name, for the query?
+3To my knowledge it doesn't use a different authentication than windows and no it does not have a different name.
+3I'm trying to see if there is another way of pulling the same data using Active Directory using a list lookup control, if this SQL control doesn't do the trick for me
+5Maybe the production connection takes longer than 10 seconds? Try increasing your Timeout limit? Although I know 10 seconds already seems like forever to a user to wait for data to populate....
+3the time change didn't work and I am looking at this example right now of Query LDAP Action ....no I actually never heard of this tool until today...I'm very new to Nintex
https://community.nintex.com/t5/Nintex-for-SharePoint/Display-meaning-full-name-from-Active-Directory/m-p/9129#M7682
https://community.nintex.com/t5/Nintex-for-SharePoint/Display-meaning-full-name-from-Active-Directory/m-p/9129#M7682
+5Sorry, I deleted the Query LDAP comment because I realized immediately after posting it that you're asking about a form not a workflow... But if it's somehow helpful, great! :)
+3yes i'm working in a form and not a workflow and I'm realizing this may not be what I need...the SQL is what i'm mostly familiar working in but I'm just baffled its not showing the data when I publish the form.
+5Especially since it works in your testing environment - it seems there would have to be a way to get it to work in production as well. Sometimes I've found with Nintex Forms that if you just delete a control altogether and then create it again from scratch, even if all the settings are identical to what you had before, the new one will work. Might just be a migration hiccup.
+3I figured out a work around using AD and the userprofilelookup command in my control, thanks for your assistance overall.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.