How do I stop errors in SmartController following the MyBepoz shut down?
After migrating from MyBepoz, some customers may experience recurring errors in their Smart Controller. This article outlines the cause of the issue and provides a quick workaround to resolve it.
Step-by-Step Instructions
1. What’s Causing the Error?
Post-migration, the MyBepoz ID remains stored against the customer records. The Smart Controller continues referencing this ID, leading to repeated error prompts.
2. How to Fix It
There are two methods to resolve this issue.
Option A: Manual Removal via Maintenance Operator
1.Open the Maintenance Operator.
2.Navigate to the Customer module.
3.Locate the customer record.
4.Find the field labelled MyBepoz ID.
5.Delete the contents of this field.
6.Save the customer record.
💡 Repeat this for each customer experiencing the issue.
Option B: Use a Script (Advanced)
If you’re comfortable with scripting, you can attempt to remove the MyBepoz ID in bulk.
Script Part One:
UPDATE dbo.OpMyBepoz
SET MYBEPOZID = 0
WHERE MYBEPOZID > 0;
COMMIT
And second just to clean up/delete the OpMyBepoz entries
BEGIN TRANSACTION;
DELETE FROM dbo.OpMyBepoz;
COMMIT TRANSACTION;
Best Practices
•Always back up customer data before making bulk changes.
•If unsure, use the manual method first to test the outcome.
•Involve your internal technical team before using scripts.
FAQs
Q: What is the MyBepoz ID used for?
A: It’s a legacy field used to identify customers in the MyBepoz ecosystem. Post-migration, it is no longer required.