Data Generation

Overview

This tool can be used to quickly generate multiple rows for each of the application transactional tables to easily support database load testing.

Key Features & Functionality

  • Reads database metadata to automatically pull tables and columns
  • Provides multiple generators for generating data of different types (users, groups, folders, documents, location data, health data, personal data, etc..)
  • Connects to Appian database to generate and populate data in one step - MariaDB, PostreSQL, SqlServer, and Oracle sql setup scripts included
  • Supports the addition of new generators

If you have ideas for more generators, please leave a comment!

Anonymous
  • I have just installed the Data Generation app and wanted to let others know of an issue I managed to get around. We are running with GB locale, and I think anyone else wih this locale will have the same issue I had. Two of the Process Models in the zip were invalid and prevented the import completing. The names for process models with guids 0002e471-1998-8000-fd81-024d98024d98 and 0002e982-5049-8000-418b-014d98014d98 were empty for GB locale. I edited the xml files and copied the US locale names into the empty <value> tags for GB, updated the zip, and it then imported successfully.

  • v2.0.0 Release Notes

    New Features:
    • App updated to 22.3
    • Now uses OOTB execute stored procedure
    • UX enhancements
    • New Generators
    • Next available primary key
    • UUID
    • Postgres Support
    • Support generating to multiple data sources
    • Updated documentation
    • Added process to re-sync records after data generation
    Bug Fixes:
    • Added more comprehensive generator errors
    • Run a delete on a table without inserting data
    • Fixed mariadb issue with too a table with too many columns
    • Fixed re-enabling of constraints after data generation
    • Issue with preview not updating

  • Is the schema correct? If you run the stored procedure directly with those inputs do you get any response?

  • Hello I've been having issues here where it cannot get the tables any idea on how to fix it? I've also added the two procedure DG_GetTableColumns and DG_GetTable

    ...

  • Do you have any suggestion on how to fix the data store issue?

  • To meet this use case you would order the inserts so that entity occurs first. Then on the store and product generators you select foreign key for the entityId column and point at the Entity pk column.

  • Those errors don't seem related to properties files issues, they seem to be due to a data store issue.

    For your previous issue, when you uncommented the lines you corrupted the properties file. The only lines that should be uncommented in that file are content.<uuid>.VALUE lines like 35 and 43.

  • Sorry for the late reply. Yes, I've tried importing it without changing anything on the properties file and this is what happens when I inspect it before importing it.

  • You shouldn't be uncommenting those rows in the properties file. Did you try importing without making changes to the properties file?

  • Good Afternoon

    I tried importing the data generation on the environment

    I updated the Data Generation Application Properties file and updated the line 29, 30 and 37,38. First I remove the pound sign and change the colon (:) to equal (=).

    Then I imported it like this

    after that I inspected it before importing to check if there are any errors since there are no errors, I proceeded to import it.

    then when I imported it, the status is failed.

    Then when I checked the import log this is the error that are written

    Has anyone how to solve this error? Thank you