Hi Laurence, 
Are there any entries prior to that in the Trans. Log tab that show the field quote was actually received on the mobile technician’s device?  (is there a chance that the tech that you assigned the quote to was not logged in and using the application and the quote was later reassigned to a different mobile technician?)
If that doesn’t appear to be the case then check the Node value that is entered on the Field Quote record and check the Node Security settings for the mobile technician (if the tech doesn’t have access permissions to that particular node then it could explain why it was never dispatched and received on the mobile device previously).
Thanks,
Reid

Hi Reid, 

Thank you. Yes it can be the case. This occures mainly, when the service order status is updated later on on back-office. 

But the goal of my question is then to identify if this could cause the issue : the ‘is_sent_to_mobile’ flag in DB is not set to N (staying to Y), even if is_exclude_mobile is Y.

Thank you

Hi Laurence, I ran some tests and once I set the Exclude from Mobile flag in the Field Quotation module the is_sent_to_mobile field at the database level gets flipped back to N for me at that time, so I can’t replicate the issue.  Give it a test on the QAC environment and see if you can replicate it there.
Thanks,
Reid

Thank you Reid.

Unfortunately, I did run some tests as well, and was not able at this point to reproduce. But having a look in the database, we can see that this is not a single case. Thousands of records are concerned …

Any advice to solve that ? 

Hi Laurence,
Take a look further back in the Trans. Log...see if you see any patterns for records where it happens and records where it doesn’t.  i.e. are any other fields changed at the same time as the Exclude From Mobile flag is set?  (look for trans log entries that are created at the same time...did the user flip that flag and update some other fields at the same time and then press Save one time?)  Are any process flows or integrations touching the order at the same time?  Or are all of these changes only being made by users in the Alliance application when the issue occurs?  Also check the Alliance Event Viewer log files (if you can identify any recent examples via a DB script then you can probably search through the log files to see if any errors were captured at the time the exclude flag was getting set).
Thanks,
Reid