marie
Cannot find field metadata item for field name somethingDeleted on object person
I see - thanks a lot for your feedback, that's very useful for us!.
As you may have guessed, we are trying to log an activity on a no-longer-existing field.
I have created a bug report that we will try to tackle soon, but in the meantime, you should be able to unblock yourself by deleting the rows logging the change of activity on the deleted fields from your workspace's timelineActivity table; in your specific case from the window, rows containing properties with isACoolGuy (eg
{"diff":{"isACoolGuy":{"after":false,"before":true}}}).10 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Hi @Rob , I started investigating but could not reproduce on my end - I will further investigate tomorrow and keep you posted, thanks for your patience
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Thanks @Rob !
Can you confirm you are trying to migrate from to v0.22 from 0.21 and not from an older version ? If not, that could cause issues.
Also, would it be possible for you to dm me a dump of your db so I can try to reproduce locally ?
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Hi @Rob thank you!!
About your issue, the issue from the upgrade-0.22 command is not critical at all, but the one in sync-metadata is more annoying.
In our latest version we transitioned the standard field on company "address" to a new "address" composite field that contains subfields such as street, city, state etc. The sync-metadata script is supposed to deprecate the previous version of this field (by renaming it address_old and updating its fieldmetadata value isCustom to true) and introduce the new one (by creating a new address field). Your error indicates that the field with the name "address" already exists; maybe the deprecation of the old address field failed for some reason.
Could you please show me
- what are your pending migrations (metadata > workspace migration > sort by "applied at" desc to get the most recent ones)
- which address field you have in your fieldMetadata (metadata > fieldMetadata > filter by name "address"): the whole row
Thank you for your patience !
36 replies
Errors thrown when adding fields
Hi again Rob - you have identified the right issue. It's something we will work on soon, in the meantime I have no real workaround to suggest to you, except to avoid creating this many fields, which is a serious limitation I know! As stated in the issue the problem is that we query all object's fields in some queries and hit the pg_graphql/postgres limit
14 replies