How to identify BBCRM or ODS connection issues

# How to identify BBCRM or ODS connection issues

Login to production member center with your test user.
Open up a development console by right clicking in a browser window and clicking Inspect.
Locate a Network tab in a list. Reload the page & see the data in the network list populate.
Search for stcp.azure, if you see 200 code next to all those codes, ODS is up and running.
Search for lo-bbis, if you see 200 code next to all those codes, BBCRM is up and running.

Anything other than 200, likely means that the service is down.

Locate your test constituent account in Luminate; copy & paste field values for Member ID and Exchange ID fields into a text editor and save.
Locate the desired member, let's call them Janet Doe, in Luminate, copy their Member ID and Exchange ID fields.
Paste the desired member values into your test account.
Log out and log back in as your test constituent.
ODS and BBCRM data will be pulled in based on those two values, those elements should be visible in the test user's account.
After testing is done, or within 1hr, whichever one is sooner, update your test constituent account with your original Member ID and Exchange ID fields. This will ensure that the sync process does not run into conflicts seeing 2 users with exactly the same unique ids.