You are uploading information from a database source to DocuWare Cloud and cannot find all the data?
When processing data from your local database, you only see (the same) 1,000 rows?
When using Local Data Connector, you are limited to 1,000 rows when processing data with Auto-Index or with a Workflow.
Workaround / Question: Is there a way to disable the 1,000 row limit?
Workaround / Answer: The 1,000 row limit cannot be disabled. This has been firmly set for a variety of reasons, including but not limited to performance and network utilization.
To evaluate how much data you will process, it is a good start to check directly with the database, you are collecting the information from.
Connect to your respective database and evaluate the tables / views you want to connect to DocuWare Cloud.
If you do not have direct access to the information, pass this on to your third-party data provider or check within your external system (e.g. ERP Software).
Each database has their respective client, there are also general tools available. To mention a few important ones: MySQL Workbench, Microsoft SQL Server Management Studio (SSMS), ORACLE SQL Developer.
When you have identified your tables or views you want to import to DocuWare Cloud, you can check the number of records by using SQL statements or the client's features.
Should your tables or views contain more than 1,000 rows of data, you have the following options:
- Create filtered views on the database directly
- The important part is the WHERE clause
- Export your database data and import it via file-connection KBA-36575
- We have a filesize limitation of < 4 MB
- This option is especially helpful, for one-time import of data
- First, evaluate the relevant data that should be processed by DocuWare
- Columns that are not required in DocuWare Cloud should also not be part of the view. Only specify the columns you require.
- Avoid using the "SELECT *" command
- Always include a "WHERE" clause in your view
- The filter condition (WHERE) should limit the data to < 1,000 rows
- Ideas on the limitation e.g. active entries, the last change is within the last few days, limited by the document or supplier type etc.
- Second, check the data type of the values within your database and potentially convert them to match the value within DocuWare Cloud
- Third, reduce the complexity of the view by limiting the "Join" operation as much as possible. If possible, create a new dedicated view for your use-case.
- Our experience has shown, that complex views are more error-prone, especially performance wise
- Fourth, if you require writing back to your database, please check the conditions for your database when using views