You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code fake data generation was developed some 6 years ago, and has never left the experimental stage, at least according to the documentation
What I can tell from the code:
fake data generation was developed with using the existing field values in mind: values are randomly chosen from the values in the scan report
if field values are not in the scan report, like in your case, there is some code present that attempts to generate completely random data
for generating random data, the type of the fields is used, and some types, like Date and Float, are not supported
if the scan report contains no types for the fields (e.g. when run on csv files), no data will be generated
if the scan report contains a zero (0) value in the the "N rows checked" column(s) in the "Table Overview" sheet, no data will be generated at all. This will be the case when "Scan without Field Values" is ticked; you can of course circumvent this by changing the 0 to 1 for each table you want to have data for, but then you still end up with random data (or incomplete data), for which I cannot see much value.
There is no simple, obvious and meaningful fix for this use case, as far as I can tell.
Describe the bug
Generating synthetic data from a scan report without Field Values results in empty CSV files
To Reproduce
Expected behavior
Something in the CSV files
The text was updated successfully, but these errors were encountered: