gospel

Thank you both @GrantSmith and @MarkSnodgrass , am all set.

Thank you @MarkSnodgrass , So start with the highest bucket like More than three months, then slide down to the cases with weeks.

Thank you @MarkSnodgrass Will take a look.

Ah ok - Let me look into that. So it will look something like this? @GrantSmith

@GrantSmith it will always be two. I have a primary evaluator and then someone who would randomly audit their work but it’s always two. one evaluator and one who audits the evaluator randomly

Update: Turned out to be an issue tier 2 support had to resolve.

@MarkSnodgrass Thank you. Had a zoom call with support today and they are looking into it, def seems like a bug in the process.

Hi @jaeW_at_Onyx Thank you for your response btw

Hi Jae, It seems like a bug. The bm field was created at the card level and published into the dataset (checked the box to share with dataset). The shared field also exists in the subscriber's instance - just does not auto recognize the field as the ID seems to be missed? I deleted the subscription and tried again, still…

Thank you both! It worked out :)