RE: Booking Status readonly on Mobile (Woodford)
I have encountered same problem - with other fields also. It's because Microsoft have some offline HTML code for the BRB that's overruling. (Actually they have just overtaken old Field One code and haven't bothered looking into this and mainly replaced all f1_ with msdyn_) In a lot of scenarious it seems like Microsoft are using this approach using offline html - and proberly because they didn't bother chaning it. You have to know what you are doing but a solution is to comment as many of those Microsoft customizations out as possible or remove them in the brb.js - however since Microsoft have done it this way you are risking to break something else. In fact i don't see why they have done it this way since all that coding could be done by simple woodford rules.....!
it's this code that's causing it. Actually i think i ended up just renaming the General tab in BRB in woodford to break the code... This also broke some other code enabling/disabling different fields in BRB that Microsoft thought was a good idea...! So win win
setBookingStatusFieldIsEnabled: function (entityForm) {
var detailView = entityForm.getDetailView(FS.Common.TabNames.BRB_BookingTab);
var bookingStatusItem = detailView && detailView.getItemByName(FS.Schema.BookableResourceBooking.properties.bookingStatus);
if (detailView && bookingStatusItem) {
// disable booking status field if it's already disabled or if status is Completed; enable it otherwise
bookingStatusItem.isEnabled = bookingStatusItem.isEnabled !== false ? FS.BookableResourceBooking.currentFSStatus !== FS.Enums.msdyn_bookingtimestampmsdyn_SystemStatus.Completed : false;
}
},