Simon H. Hellmann Toshiba Tec Germany Imaging Systems GmbH IT-Consultant Document Management Solutions

Dann fällt mir nur noch ein, dass das Feld zur Volltext-Suche in diesem Suchdialog vielleicht anders benannt ist als in allen anderen.
Ansonsten gerne ein Ticket beim DW-Support eröffnen, die sich das Problem auf Ihrem System anschauen können.

Gruß aus Neuss,
Simon H. Hellmann
DocuWare System Consultant

Hallo Lena Diez,

vermutlich ist in dem Archiv, auf welches sich der Suchdialog bezieht, die Volltextsuche nicht aktiviert.

Gruß aus Neuss,
Simon H. Hellmann
DocuWare System Consultant

Thanks for reporting back.
Yes, I also forgot that the keys are case sensitive and did not catch it in your messages.

Anyway, now we have a great thread we can point to in the future if someone else has issues with the dwcontrol syntax! (;

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Sounds pretty strange.
The last thing I can think of is the encoding.
Please make sure your .dwcontrol file is saved as UTF-8 (without BOM) and your first two lines of the file should be these: 

<?xml version="1.0" encoding="utf-8"?>
<ControlStatements xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://dev.docuware.com/Jobs/Control">

If it's not that either, please open a support ticket with DocuWare and have someone from the support team look at this.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Okay. Try to use the fieldName whenever possible, FieldLabel can be changed at any time and then the configuration might not work anymore.

Pivoting to other ideas: Are your 100% sure that the DW user account which you are using in the DW Import is allowed to write into the field?
Does the user have the permission to write, change and create new entries in this index field or maybe that right is missing from some custom file cabinet profiles or index value profiles?

Does the store dialog set the field to read-only? Does the import configuration overwrite the entry with an empty one?


If you are on DW on-premise, you might also be on that one version with a bug where DW Import uses the currently signed-in windows user instead of the user which is logged into the desktop apps to store documents. Update DW if this is the issue.

Hope this helps.
Greetings from Germany,
Simon H. Hellmann

Hi Michal Cepek, 

the format I always use is this: 
<Field dbName="AMOUNT" type="Decimal" culture="en-Us" decimalPlaces="2" value="4688.6000" />

Maybe the dbName is case sensitive and you need to type "CASTKA"? Or maybe the field has a different dbName and you just typed the display value? Everything else seems to be about the same as in my line.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hi Miquel Sanz Vargas, 

you can have multiple dialogs with Intellix active, no problem.
However, as Intellix is run instantly when a document is stored in a basket, the basket is directly linked to the store dialog, and thus, to a specific Intellix configuration. So you need to have as many baskets as you have store dialogs with Intellix.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Mariya Tsvetkova,<br> <br> yes, you should be able to do that using the Platform API with the webservice activity.<br> This is the route you need to use:&#160;<br> <code>POST https://{{DocuWareServer}}/docuware/Platform/FileCabinets/{{FileCabinet-GUID}}/Documents/{{Doc-ID}}/Annotation</code><br> <br> Position is optional - if you give no position information, the API places the stamp in a convenient position, just like a normal workflow task stamp.<br> If you want to include the position, remember that the API expects twips as the unit of measurement.<br> <br> Hope this helps.<br> Greetings from Germany,<br> Simon H. Hellmann<br> DocuWare System Consultant

Hallo Andreas,

ein Support-Ticket hier bei DocuWare sollte schneller und günstiger zum Erfolg führen.

Gruß aus Neuss,
Simon H. Hellmann
DocuWare System Consultant

Hi Daryl,

as far as I know, DocuWare 7.10 does not have any functionality built-in for this.
I have the same problem in multiple customer systems, and my workaround is currently a custom C# application which uses the REST API to modify the data in the table fields.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant