-
Hi-
You don't need code for this. You can use rules.
You can add a field to your schema and call it Status. Then add on load rules to switch views according to the value of the Status field.
You can have multiple views, modify some of them so that they are read only, and then set up rules to switch to the correct view.
Hope this ...
-
Hi,
This should be pretty easy. Simply add a button to your view, and then click on File > Manage Rules. Add a new action, then add a rule to switch views.
Can you try this and let us know whether it works for you?
Thanks!
-
Hi,
I'm sorry you've encountered this issue.
Could you please open the DBXL Administration Tool (DAT) and check the Licensing screen?
I'm curious whether you have an expired trial license, or whether the license you have does not include QueryDB.
You can attach a screenshot of the Licensing view via the Options tab when ...
-
Yes, this is a security risk. Even if you use views or conditional formatting in the form, the xml is still out there for download.
We've used the Encrypt command in qRules to encrypt the data. Whether you use qRules or not, I think the solution is encryption, such that the xml data is not readable if downloaded.
-
Please try admin-deploying the form instead of sandboxing, and let us know how that goes.
When sandboxing, SharePoint uses a service account, which means if you call a web service such as the UserProfile it fails. We've seen this with our own DBXL web services and the solution is to admin-deploy.
Since you mention UDC files, I wonder ...
-
Then the solution is to put the radio buttons themselves within sections, so you can hide/show those sections as desired. :) Can you try that?
-
By using conditional formatting you can hide/show sections as desired.
If the field for a radio button is equal to False, then hide this section.
Make sense?
-
Hi-
I'm not sure that I understand the issue.
Each view is independent of the other. If you want fields 1, 2 and 3 in View1 but only fields 2 and 3 in View2 that is very easy. Just design your canvas to only have the fields you want.
You don't have to transfer anything; the values are stored in the schema itself. The only fields shown ...
-
Hi Scott-
You should replace the
QdabraRules.xml, QdabraRules.xsd and the DLL. Just to be sure, you should
also replace the qRules DLL in the code project and rebuild the project.
I don't have experience regarding your second question, but I'll ask the team.
Thanks.
-
No. If you inject to a newer version (say you were using the v3.3 trial and injected to v3.4) a command could have a new parameter or a change in behavior. But, in general, this hasn't happened in the most recent versions and I don't believe any issues will arise from v3.3 to v3.4.