Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Point Radii Implementation
-
Fix Version/s: Point Radii Implementation
-
Component/s: None
-
Labels:None
-
Environment:
Environment : ST2
Build details
SMS Core: P18
SMS Service: P7
Description
When we redeploy a bing account which contains 1603 as SAID then its failing.
Steps to reproduce.
Step 1: Get a legacy account or create a new one with production build.
Step 2: Add proximity target for 1603 and redeploy in new build after.
Step 3: Redeploy with new build.
Expected result: Should update the new proximity in the database and ad center.
Actual result: Throwing exception.
Please find attached log and snap shot.
We checked in production database there are 2 accounts which were deployed have SAID 1603.
One is in deleted state BPID 0013986166
One is in Active state BPID 0010816492
