-
Hi -- is the issue then item 3 -- that when you delete from SharePoint, the document is not deleted from DBXL? I don't understand the question in item 2?
-
A couple of things you might try to troubleshoot -- grab the secondary data source that is populating your control and drag it onto your form someplace, so you have a repeating table or section that shows everything from your list. Preview, and see how many records are in the data source.
If you are still getting only 6, you might want to try ...
-
Just use a formula for the default value for your "Total" field and use the Insert field or group button to select each of your fields. Then put a + sign between the fields....
-
Ah, I see. What would happen to the form name if the user opened it after the form was submitted and changed how many checkboxes were selected? Could that happen?
-
Hi -- not knowing a thing about your data structure (like where the fields are that are bound to your checkboxes) I put together a simple sample that counts 'true' values and concatenates them with a date in a default field value. Right click the link to the file in the header to this post and save it locally. Right click the saved file ...
-
You can overcome this by changing your last condition to "The expression" and use "and" or "or" as needed to create your compound condition. So, for example, if you need to make sure both field1 and field2 are not blank, you'd use the expression:
my:myFields/my:field1 != "" and my:myFields/my:field2 ...
-
Hi:
Do you mean assign the field value? Or the data source that provides the options to the combo box?
You can use a secondary data source for your combo box options (probably an XML file would be the best option) then in code populate the XML file with the options you want available.
-
Actually, you can rename your promoted property columns without changing your data source names, I think. Under Tools / Form Options / Property Promotion, you can modify a promoted field, and type a new name for it in the column name. I'm not sure if your existing xml will have to be reopened and saved to then display their data in the newly ...
-
See my reply to your thread here.
-
I would suggest that you create a new form and connect it to your database using Windows authentication. Then, save that form as source files. Examine the connection information in the manifest.xsf and in a copy of your production form that you have saved as source files, modify the connection strings accordingly.