Field Service in Dynamics CRM is massive – lots of entities, lots to configure, lots to learn. One of the nicest features on my books is a Resco-based mobile app, Field Service Mobile, fast and user-friendly.
When Field Service Mobile starts for the first time, it may display an error message:
Exception while fetching entity msdyn_agreement
Server Error: Code.Value=s:Sender| Reason.Text='msdyn_agreement' entity doesn't contain attribute with Name = 'transactioncurrencyid'.| Boring details.
Looks like developers of the app had a different schema from the one deployed by the trial. The workaround is to create a dummy currency field in Agreements entity and then immediately delete it. That will create transactioncurrencyid and exchangerate system fields and leave them there permanently. Restart the app and you’re good to go.