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
We integrated Frictionless for validating CSV files, and we are receiving validation responses as expected. However, we need to retrieve the original processed data in JSON format, parsed directly from the input CSV, along with the validation response.
Could you kindly confirm if there is a built-in method or API endpoint within Frictionless that allows us to obtain the parsed JSON data along with or after the validation process? If so, any guidance or documentation would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
To clarify, we are successfully receiving the validation report in JSON format using the validate method. However, along with the validation report, we also need the actual data from the CSV file in a JSON-like format (e.g., rows parsed into dictionaries or similar structures).
We are aware of the extract method, which allows parsing CSV data into JSON. However, we would like to know if this data extraction can be done directly within the validate process, avoiding the need to handle the file separately for validation and data extraction.
Could you please confirm:
If there’s a built-in feature in validate that supports this functionality?
If not, would you recommend combining validate and extract programmatically to achieve this?
Any guidance or suggestions would be highly appreciated. Thank you!
We integrated Frictionless for validating CSV files, and we are receiving validation responses as expected. However, we need to retrieve the original processed data in JSON format, parsed directly from the input CSV, along with the validation response.
Could you kindly confirm if there is a built-in method or API endpoint within Frictionless that allows us to obtain the parsed JSON data along with or after the validation process? If so, any guidance or documentation would be greatly appreciated.
The text was updated successfully, but these errors were encountered: