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
Please describe the feature you have in mind and explain what the current shortcomings are?
When CSV ingest is used to ingest renders from vendors, it is not easy to communicate the full folder path. It would be great to allow a fallback that tries to match the folder path from .csv against all folder names in the project. Folder name is not unique identifier, but many projects still enforce the perfectly reasonable limitation of unique folder names per project.
How would you imagine the implementation of the feature?
The CSV Folder Path column should be first matched against project folder paths, and the failed items agains project folder names. Maybe this should be optional so the current behavior is preserved.
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
Alternatively, another column named Folder Name can be added, and ingest would use it only if Folder Path is empty. This would be more explicit, but would add another column and we already have a lot.
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
When CSV ingest is used to ingest renders from vendors, it is not easy to communicate the full folder path. It would be great to allow a fallback that tries to match the folder path from .csv against all folder names in the project. Folder name is not unique identifier, but many projects still enforce the perfectly reasonable limitation of unique folder names per project.
How would you imagine the implementation of the feature?
The CSV
Folder Path
column should be first matched against project folder paths, and the failed items agains project folder names. Maybe this should be optional so the current behavior is preserved.Are there any labels you wish to add?
Describe alternatives you've considered:
Alternatively, another column named
Folder Name
can be added, and ingest would use it only ifFolder Path
is empty. This would be more explicit, but would add another column and we already have a lot.Additional context:
No response
The text was updated successfully, but these errors were encountered: