nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Missing value in uncommitted batch - Finder number

Young Lee

Somehow, finder number is not showing in an uncommitted batch as attached screenshot.

Finder number has been mapped and it has been nominated but only in a batch.

Please let me know any solution?

bbis-community.png

Find more posts tagged with

Comments

Brennan Hadden

We have seen this having for a lot of different reasons, but BBEC usual tell us why. In this case, how did you get the finder numbers in the batch? Is this an import issue? Does the batch have marketing information? I noticed some of the rows have warnings on them. Does the warning help? Or is finder number working as expected and just not displaying?

Hope this helps to point you in the right direction.

Brennan

Young Lee

Brennan Hadden:

We have seen this having for a lot of different reasons, but BBEC usual tell us why. In this case, how did you get the finder numbers in the batch? Is this an import issue? Does the batch have marketing information? I noticed some of the rows have warnings on them. Does the warning help? Or is finder number working as expected and just not displaying?

Hope this helps to point you in the right direction.

Brennan

Hi Brennan,

Thanks for your response.

In short, finder number is working as expected but it is not displaying within a batch.

And there is no marketing information (This could be an issue too).

As you noticed some rows have warnings with physical addresses. I believe this is not causing the issue as finder number is still not displaying in no warning.

Would you have any other suggestions for us to try?

Thanks,

Young

Brennan Hadden

Hi Young,

I would check the marketing effort and make sure it is activated. I would also use query to check the finder number is attached to someone's record.

Hope this helps.

Thanks,

Brennan

Sabra Aaron

We have seen this issue -- it was introduced in SP21/22, and seems to be a case Blackbaud Checkout not passing the finder number into CRM batch data; it will also not pass Appeal codes that you might be passing in through a URL string (&source=[appeal%20code%20here]). You might want to contact Support because they may be able to supply you with a javascript interim fix that writes finder number and appeal to revenue attributes instead of using the native fields. You can then copy the ersatz finder number into the native field during batch review and it will pull in all the associated marketing effort information. Hope this helps!

Young Lee

Brennan Hadden:

Hi Young,

I would check the marketing effort and make sure it is activated. I would also use query to check the finder number is attached to someone's record.

Hope this helps.

Thanks,

Brennan

Hi Brenna,

Marketing effort is activated. I will have a look and use query to check the finder number is attached to others' record.

Thanks,

Young

Young Lee

Sabra Aaron:

We have seen this issue -- it was introduced in SP21/22, and seems to be a case Blackbaud Checkout not passing the finder number into CRM batch data; it will also not pass Appeal codes that you might be passing in through a URL string (&source=[appeal%20code%20here]). You might want to contact Support because they may be able to supply you with a javascript interim fix that writes finder number and appeal to revenue attributes instead of using the native fields. You can then copy the ersatz finder number into the native field during batch review and it will pull in all the associated marketing effort information. Hope this helps!

Thank you Sabra!

I will contact Support to have a look at this issue, meanwhile I may keep trying to resolve!

Much appreciated.

Young