Some users can’t save records and this is what shows on consol
Good morning Leo, hope you slept well. Customers just send me this when trying to save records.
Error is:
ERROR Error: Cannot reference blabItems with IDs 51959543,51959591,51959651,51959675 from multi-relation flimDef: 215578
l tape-gql-error.class.ts:3
g gql-error-handler.operator.ts:27
RxJS 3
Angular 11
Hi @Leo ,
sometimes I get a similar error when trying to create a new item in a certain app.
Checking the console I found those errors:
core.mjs:9095 ERROR c: invalid byte sequence for encoding "UTF8": 0x00
at T.selector (https://tapeapp.com/main.d420f0be4a62c0aa.js:1:466351)
at T.error (https://tapeapp.com/vendor.f9a07d4ab9103d41.js:143:242417)
at W._error (https://tapeapp.com/polyfills.6bcf5f2d8583f40b.js:1:9305)
at W.error (https://tapeapp.com/polyfills.6bcf5f2d8583f40b.js:1:9102)
at https://tapeapp.com/vendor.f9a07d4ab9103d41.js:65:42015
at de.invoke (https://tapeapp.com/polyfills.6bcf5f2d8583f40b.js:14:6596)
at Object.onInvoke (https://tapeapp.com/polyfills.6bcf5f2d8583f40b.js:1173:774)
at de.invoke (https://tapeapp.com/polyfills.6bcf5f2d8583f40b.js:14:6533)
at Ae.run (https://tapeapp.com/polyfills.6bcf5f2d8583f40b.js:14:1857)
at https://tapeapp.com/polyfills.6bcf5f2d8583f40b.js:29:2862
of course we can help you. Creating a record is a core process and must always work.
How are you trying to create the record where the creation fails? Manually via record creation, automation, API or email?
Have you possibly set a relation in the creation via template, view creation or duplication of existing records?
There have often been problems here in the past because the user does not have permission to the linked records, but there is now a setting for this.
I’m trying to create the record manually, without using any template.
I tried to create it within the generic “all items” view, but nothing changed.
Of course I have set different required and relationship fields, but everything is filled correctly.
On the frontend there’s no errors at all
I don’t think it relates to permissions, because I’m the admin of the organization.
We checked our logs and were able to trace down a problem with input validation, that would lead to this error for certain provided input values on record creation.
We just deployed a fix that should resolve the issue. Could you verify on your end, that you can now create the record as expected using the same inputs as you were using by the time of the report?