InfoPath Dev

Hola, que tal? En el formulario de InfoPath seguro tienes una conexión que envia datos a SharePoint. Al configurar esta conexión, tienes que decidir el nombre del archivo. También tienes que decidir que hacer cuando ya existe un archivo con el mismo nombre. Por ejemplo: Digamos que tu formulario tiene un nombre - "Fulano" - y utilizas ...

Hi Tobias, I'm sorry you're having issues. Your English is easy to understand, so don't worry about that. The first thing I notice is that your source and destination don't match: one has 3 fields and the other has 4. This may be causing CopyTable to fail. The qRules secondary data source contains an error node. Would it be ...

The issue is that the source data is stored in XML, not in the database. So your third party software is modifying a copy of the data; there's no way (that I know) for the third party software to edit the xml and resubmit it to the Qdabra web service. Throughout this process, DBXL is the "owner" of the XML, the XML is edited via ...

You'll need to modify the first action in the rule (from the screenshot you included above). Right now you have: Next_Estimate = concat("<query... But you need queryxml = concat("<query... Where queryxml is a node in the secondary data source you created to query the database (NextEstimateNumber).

You'll need to change the first action to set the queryxml node in the secondary data connection. The execution steps then become: 1. Set the value of queryxml of the the query data connection 2. Execute the query data connection 3. Set the desired field to the result obtained from the query data connection

 Also, comparing your query strings I notice:you're using #CORLOG# in one and CORLOG in the other (for the database parameter).You have a maxrows of 1 in the concat statement. If you are filtering, and you expect to only find one matching value, then the maxrows parameter won' t be necessary.<query database='#CORLOG#' ...

For more information on using QueryDB, check out these links: QueryDB User Manual Implement Static and Dynamic queries using QueryDB

This could be related to the permissions for the user accessing DAT (DBXL). Usually that error code occurs when a user tries to perform an action in DBXL for which they have not been granted permissions. Does the error I0033 show any other details? Perhaps in the Event Viewer for Qdabra? (like Ted asked) Our first step should be to look at the ...

To accomplish what you describe I use the DateDiff command in qRules. We created this toolset to save on development/coding time. Perhaps it'll help; read more here.