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
In some cases, it could be useful to trace back to specific csv files that supplied rows of data. For example, if the files are backed up in dropbox and have audit significance.
Today, the best workaround is to copy and paste a file name onto all the new rows right after importing or perhaps
to use a new record trigger that look it up in another table based on date (or something like that).
Describe the solution you would like
I would like grist to provide 1 additional field of the file name being loaded in which can be mapped to a column of the table.
Obviously, the default name would have to be carefully chosen (something like grist_import_file_name) to avoid name conflicts as best as possible, but at least I know grist has access to the file name since it because the default table name for new tables.
It might also be that this minor convenience isn't worth it on it's own, but becomes more worthwhile if there's other metadata that be persisted with imports on the row level.
The text was updated successfully, but these errors were encountered:
Describe the problem to be solved
In some cases, it could be useful to trace back to specific csv files that supplied rows of data. For example, if the files are backed up in dropbox and have audit significance.
Today, the best workaround is to copy and paste a file name onto all the new rows right after importing or perhaps
to use a new record trigger that look it up in another table based on date (or something like that).
Describe the solution you would like
I would like grist to provide 1 additional field of the file name being loaded in which can be mapped to a column of the table.
Obviously, the default name would have to be carefully chosen (something like
grist_import_file_name
) to avoid name conflicts as best as possible, but at least I know grist has access to the file name since it because the default table name for new tables.It might also be that this minor convenience isn't worth it on it's own, but becomes more worthwhile if there's other metadata that be persisted with imports on the row level.
The text was updated successfully, but these errors were encountered: