Anyone have errors when deploying a custom record?...
# sdf
w
Anyone have errors when deploying a custom record? My custom record object in SDF compares with no differences in both my SB and Prod accounts, but the deploy errors with:
An error occurred during custom object update.
Details: Invalid fldfiltersel reference key 5 for fldfilter STDBODYTRANTYPE.
File: ~/Objects/customrecord_as_sub.xml
Object: customrecord_as_sub.custrecord_as_sub_transaction (customrecordcustomfield)
2021-04-08 14:27:28 (PST) Installation FAILED (0 minutes 32 seconds)
r
Yes, I am having a similar error. Somehow it fails to detect that the key is fully valid. In my case is a filter in a field within a custom record. The filter references an item type that is present it all accounts. Yet when trying to deploy in some accounts, I get a similar error. Saying that the reference id (they) is not valid. Which is false. Workaround is to do manually the same in the target account, which is annoying.
w
@Roc127 Same. This is a filter in a custom record field.
r
I am pretty sure is a bug. I have not open a ticket with support, hopefully there is enough information for the SDF team to replicate it and fix it.
I am still getting the error describe in this bug. Just wondering if the sdf team is aware of such bug.
a
Hello, there was an issue similar to this which was resolved in a previous release. Since you're still experiencing it, please do open a ticket with support so that it can be passed on to our team.
👍 1
m
I ran into this same error today. I noticed that if I delete the field in the UI and then deploy, it works the first time round but fails with this error on subsequent deploys.
@Roc127 @wes_w do you have a defect number?
Support has filed Defect 628216 :  SDF > Deploy custom field > Invalid fldfiltersel reference key 105 for fldfilter STDBODYTRANTYPE for me
r
No, sorry, I did not go through support yet. I do still experience the error
m
Latest update from support. I've tested and it appears to be working correctly on that account now
The fix for the defect has been rolled out on [ACCOUNT_ID]. Would you be able to confirm if the error is still reproducible on your end?
r
Interesting, thanks for the update! I will write in this thread if I encounter the error again