Fixing user Data issues in D365

(0) Share

Report

Posted on by Mav

In d365 we do not have access to Live prod DB. There are instances when user creates bad data to trigger an incident.

As of 2012 r3 we as developers use to access the prod db and get it fixed there to resolve the incident.

How do we fix such issues on d365 with no access to prod db.

I am given to understand that any build push to Prod, MS will take 1 business day to fix. So will such issues pertaining to bad data created by end user will impact production for 1 business day ? This definitely not make sense, please suggest what am I missing here.

*This post is locked for comments

All responses (2)

Answers (0)

Mav on at

Like (0)

Report

RE: Fixing user Data issues in D365

I do know that that MS takes less time but the fact of matter is SLA is 5 hours.

End to end testing is not always pragmatic.

Also these are the issues created in error by user , so don't think testing would really add value here.

Agree that fixing data via SQL not good idea .So such issues would now be fixed by 1st replicating it in devbox, building solution in devbox and then immediately run sol in prod or am I missing something here.
Mav on at

Like (0)

Report

RE: Fixing user Data issues in D365

I think the SLA for pushing build to prod is 5 hrs. Even if it is < 2hr , does it not sound like obstacle vis a vis time we take to fix such bad data issue created by users in dax2012.