-
The solution is not as easy as adding the conditional mapping. You would need to change your form to use forms-based workflow.
As I understand it, this is the scenario:
1. Your form submits to SharePoint. This creates version 1 of document called 32.
2. Sharepoint workflow happens. (Sharepoint owns the XML and DBXL is not involved.)
3. A ...
-
Do you have a trigger on the CCN field that writes the data to another table?
-
Unfortunately Sharepoint workflow forces you to store the XML in Sharepoint, but DBXL needs to own/store the XML to handle the propagate delete and the database mapping and even the submit (because DBXL creates and injects processing instructions into every XML).
But as Jimmy says, you can accomplish all of this with conditional mapping in DBXL ...
-
Hi Brandon,
For #1, I'm confused about the "workflow" that you describe previous to the
form being submitted to DBXL. Can you provide more details?
From the description in item #2 it sounds like your InfoPath form is a database form. Is that true? Could you attach your form (XSN)? I would like to check the data connection that ...
-
The FilterOwssvr command in qRules can accomplish this. qRules validates parameters when we pass them in, and in this case, since we don't have a value for /value, it would usually fail. However, it is possible to trick the command by using this command: FilterOwssvr /dsname=owssvr /filter=Year /value="
You can try a URL like ...
-
Hi Stacie,
Did the xpath (/dfs:myFields/dfs:dataFields/ns1:GetColumnsXMLStrQueryResponse/ns1:GetColumnsXMLStrQueryResult/Rows/row/Job_Name/ddl_jobno) on the 2DS change?
-
Yes, this is possible. It's called cascading dropdowns, so you want to search for that term. There are lots of previous discussions about this; I found this thread: http://www.infopathdev.com/forums/t/13940.aspx. I've seen some good tutorials, just search for cascading dropdown in Google. Good luck!
-
Though I'm not a developer (so seeing your code wouldn't help much), others might be willing to troubleshoot your code, so you could post it if possible.
One thing I could suggest is creating a SQL view that contains tknum and the calculated Full Name, and just query that. That is, do the concat in the SQL view instead of in the InfoPath ...
-
Hi Jason,
DBXL (DAT) creates a form library for the XSN, yes, it doesn't add multiple XSNs to the same library.
As far as "users can see them, open them, fill them out and submit them somewhere
else", the form submits the XML to DBXL (which in turn can then map it into the database or the form library). So throughout the process ...
-
Hi Jason,
DBXL v2.3 needs to "own" the xsn. You attach the template to the DBXL Administration Tool and it gets accessed via that path you discovered (shown in the DAT General tab).
You can then add database and SharePoint mappings. However, DBXL still "owns" the xsn. DBXL can publish that XSN to a form library (or two, or ...