Luminate CRM duplicate merging

[[email protected]]

Thank you! I will pass along to Blackbaud. If they can't budge, would renaming the field in C&P overcome the problem with Blackbaud?

Thank you again for all your help. This is by far the best customer service I've received from any of our CRM vendors.

RS

[CnP.Support]

Good day!

Any updates?

[[email protected]]

No updates from Blackbaud. I followed up this morning. If they are unable to resolve this, would changing the name of the field in Click and Pledge overcome the namespace issue?

[CnP.Support]

Good day!

That is not easy to do. It has ramifications spreading to all applications and will require tremendous amount of testing. Every aspect of the code has to be tested. The issue is they are not referencing their field with their namespace. If we change the field name every application that is based on our system has to change their reference if they are using that field. Field names that are part of a managed package cannot be "changed". They have to be deprecated and a new field be created AND that deprecated field has to be manually deleted by "all" of our clients.. It has cascading effect.

In their case all they have to do is fix the way they are addressing their field. For them it is an improvement (bug fix) for us is a major overhaul with cascading issues spreading everywhere.

Hope you see the issue.

[[email protected]]

Understood. Can you think of another potential workaround in the event Blackbaud won't budge? The Salesforce integration was the mail selling point for us.

[CnP.Support]

Good day!

We have given this a lot of thought. Please note that the error is in Blackbaud's package and VF page. It is not at all related to C&P. Their page returns error.

Have you considered not using Blackbaud?

[[email protected]]

Moving off Blackbaud is not an option for us right now.

[[email protected]]

Blackbaud finally declared this a bug, which is great because they acknowledge the problem but now I might have to wait weeks or years for them to fix it.

We have an event on Sunday, and our team would like to have the integration live for that. On Monday, we'll probably need your help uninstalling the app. We'll definitely need mobile payment processing in January, which is also when the next LCRM release happens. Hopefully by then we'll be able to re-install the app and keep it in production.

[CnP.Support]

Good day @Rabia,

This is indeed great news.. sort of I guess! identifying the problem is typically 99% of the problem and the fact that BB has admitted it is a good sign. Not sure it is of much help for your immediate pain.

Just let us know what we need to do to help. Based on your post we do not have to do anything until we hear back from you.

[[email protected]]

Can you uninstall C&P now? We have a backup + all opportunities captures in Salesforce so we are okay with losing any transaction records.

Thank you! Hopefully Blackbaud fixes their bug by January.

[CnP.Support]

Good day!

As requested we have requested the application to be removed.

I will update this post once we have uninstalled the app.

[CnP.Support]

Good day!

We do not have access to your account. Please grant us login access so we can uninstall the applications.

[[email protected]]

Ahhh, sorry! Access is granted!

[CnP.Support]

Good day!

As requested we un-installed the app from your production instance.

Looking forward to seeing you soon, once Blackbaud fixes their bug.