(Note: I searched existing issues and found similar-sounding issues, but none related to this version of the community edition of Appsmith.)
I needed to move our app from an old vm to a new one. After pulling the app from git into the new instance I found that all of my REST API queries returned this:
AE-DTS-4013
DEFAULT_REST_DATASOURCE is not correctly configured. Please fix the following and then re-run: [No datasource configuration found. Please configure it and try again.] (None of my queries requires a default datasource, by the way.)
I stumbled upon a "fix" by editing a broken query's url. If I add a space at the beginning, it then works -- it seems it is provoking appsmith to regenerate its metadata but including a section that was missing before.
After checking in the code and comparing the metadata between the working and non-working versions of the query, I see that the "working one" has an additional "datasourceConfiguration" section under "datasource" (that's missing in the broken one). Enclosed is a screenshot of the diff.
Thank you! (Hope this helps. I spent a lot of time on this and learned a few things. ;-) )
Steps To Reproduce
bring up a new appsmith instance (in this case, the latest, v1.39).
connect it to git, and bring down the bits
REST API queries that worked previously now all return AE-DTS-4013
see description section above for what I found that seems to be the problem in the metadata.
Is there an existing issue for this?
Description
(Note: I searched existing issues and found similar-sounding issues, but none related to this version of the community edition of Appsmith.) I needed to move our app from an old vm to a new one. After pulling the app from git into the new instance I found that all of my REST API queries returned this: AE-DTS-4013 DEFAULT_REST_DATASOURCE is not correctly configured. Please fix the following and then re-run: [No datasource configuration found. Please configure it and try again.] (None of my queries requires a default datasource, by the way.)
I stumbled upon a "fix" by editing a broken query's url. If I add a space at the beginning, it then works -- it seems it is provoking appsmith to regenerate its metadata but including a section that was missing before.
After checking in the code and comparing the metadata between the working and non-working versions of the query, I see that the "working one" has an additional "datasourceConfiguration" section under "datasource" (that's missing in the broken one). Enclosed is a screenshot of the diff.
Thank you! (Hope this helps. I spent a lot of time on this and learned a few things. ;-) )
Steps To Reproduce
Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
Self-hosted v1.39