-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPM Run Load Error: Model not found #5
Comments
Have you ran a |
I see the model path after cds build but with cds deploy --to hana the /gen/ folder is re-created and csn.json is moved to gen/db/last-dev. Also, loading the data gives a load of errors of two types: and CompileMessage { |
When loaded the data using the restored /gen/ folder (after second build), got no errors. |
Yes, I'm not sure why the srv content within /gen is getting wiped out by the deploy. Seems to be not right to me. But that csn in the /gen/db/last-dev is something different. It's how cds is just keep track of the changes that have been made to any part of the data model that uses persistence journaling/Schema Evolution. cloud-cap-hana-swapi/cap/db/schema.cds Line 12 in 96b5e0a
But this isn't the complete model, it's only a partial model used internally within CAP to track changes. For the data load or any other usage of the CAP APIs you want the full model that should be in the /gen service folder. So, the whole role problem here seems to be that /gen/srv is getting deleted for some reason when the cds deploy runs. But at least there is an easy work around to just run cds build again after a deploy to bring it back. |
Ok, I see. Thanks for explaining. |
I did add two notes to the README.md about this situation and I'll enter an internal ticket to try and see if we can figure out why the |
convertData.js file errors as model path '/gen/srv/srv/csn.json' doesn't exist
The text was updated successfully, but these errors were encountered: