Support Topics Documentation Slack YouTube Blog

Something broke after v6 update

congragulations on v6 release, but is there something we, app developers on shared cloud should do so our apps continue to run as they were? Cause my app is broken now

my app id 4BAEABFC-6FEF-EB39-FFE3-162B0D48F300

this innocent looking command seems doesn’t working now:
return Backendless.Data.of(‘pendedJobs’).findById({objectId:“37F9FB64-B8D1-40A3-9652-EFBD1267AD84”})//, loadRelations: “status”
here is what it gives in log
2020-06-17 09:54:02,161 | SERVER_CODE | INFO | [11996] error Error: Provided object must have at least 2 primary keys.
at DataStore._callee4$ (/usr/local/lib/node_modules/backendless-coderunner/node_modules/backendless/lib/data/store.js:180:23)
at tryCatch (/usr/local/lib/node_modules/backendless-coderunner/node_modules/regenerator-runtime/runtime.js:45:40)
at Generator.invoke [as _invoke] (/usr/local/lib/node_modules/backendless-coderunner/node_modules/regenerator-runtime/runtime.js:274:22)
at Generator.prototype. [as next] (/usr/local/lib/node_modules/backendless-coderunner/node_modules/regenerator-runtime/runtime.js:97:21)
at asyncGeneratorStep (/usr/local/lib/node_modules/backendless-coderunner/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
at _next (/usr/local/lib/node_modules/backendless-coderunner/node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)
at /usr/local/lib/node_modules/backendless-coderunner/node_modules/@babel/runtime/helpers/asyncToGenerator.js:32:7
at new Promise ()
at DataStore. (/usr/local/lib/node_modules/backendless-coderunner/node_modules/@babel/runtime/helpers/asyncToGenerator.js:21:12)
at DataStore.findById (/usr/local/lib/node_modules/backendless-coderunner/node_modules/backendless/lib/data/store.js:224:26)
at Object. (/opt/backendless/repo/4baeabfc-6fef-eb39-ffe3-162b0d48f300/files/servercode/JS/default/PRODUCTION/handlers/custom-events/myCustomEvent.js:30:46)
at Domain. (/usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/tasks/invoke-handler.js:114:38)
at Domain.run (domain.js:370:14)
at /usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/tasks/invoke-handler.js:113:7
at new Promise ()
at execute (/usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/tasks/invoke-handler.js:52:10)
at executeTask (/usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/tasks/executor.js:82:7)
at Object.executor.execute (/usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/tasks/executor.js:191:22)
at executeTask (/usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/cloud-worker.js:45:44)
at processTask (/usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/cloud-worker.js:71:9)
at process. (/usr/local/lib/node_modules/backendless-coderunner/lib/server-code/runners/cloud-worker.js:80:5)
at process.emit (events.js:322:22)

(posted in slack general chat originally)

Hello @yuriy

Thank you for the report, I’m going to fix it right now, but while it’s not released could you change this to

return Backendless.Data.of(‘pendedJobs’).findById(“37F9FB64-B8D1-40A3-9652-EFBD1267AD84”)

or you’ve got a lot of places where it’s used?

Regards, Vlad

yes, this syntax used in a lot of places

the problem has been fixed in backendless@6.0.2, could you please verify and confirm that

Regards, Vlad

Yes, working fine now, thanks.