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
Is your feature request related to a problem? Please describe.
I need assistance in programmatically creating collection entries in DecapCMS.
Here's the scenario:
I have a spreadsheet with over 1,000 addresses that need to be managed in DecapCMS. To achieve this, I uploaded the spreadsheet as a CSV file using the file upload widget and triggered the postSave event via Address Updates collection. While I was able to read the file content and parse it to extract the data, I couldn't find a way to create entries in the "Address" collection programmatically within DecapCMS.
Describe the solution you'd like
I initially thought the CMS API would provide a method to create collection entries, but I couldn't find such functionality. A wrapper CMS API would be an ideal solution, as it could handle the complexities of different Git gateways or backends seamlessly under the hood.
The text was updated successfully, but these errors were encountered:
bkvaiude
added
the
type: feature
code contributing to the implementation of a feature and/or user facing functionality
label
Dec 8, 2024
Is your feature request related to a problem? Please describe.
I need assistance in programmatically creating collection entries in DecapCMS.
Here's the scenario:
I have a spreadsheet with over 1,000 addresses that need to be managed in DecapCMS. To achieve this, I uploaded the spreadsheet as a CSV file using the file upload widget and triggered the postSave event via Address Updates collection. While I was able to read the file content and parse it to extract the data, I couldn't find a way to create entries in the "Address" collection programmatically within DecapCMS.
Describe the solution you'd like
I initially thought the CMS API would provide a method to create collection entries, but I couldn't find such functionality. A wrapper CMS API would be an ideal solution, as it could handle the complexities of different Git gateways or backends seamlessly under the hood.
The text was updated successfully, but these errors were encountered: