Hi everyone!
 
We are experiencing an issue with scheduling an Service Appointment with the "schedule" button on the Gantt chart.
 
We receive this error:
AsignedResource: execution of BeforeUpdate caused by: System.UnexpectedException: common.exception.SfdcSqlException: ORA-00904: "T_19_WOLI_T_19_WO"."ACCOUNT_ID": invalid identifier ()
 
Scheduling an SA works when draging and dropping manually or using the "candidate" button on the Gantt.
If we manually change the assigend resource we receive the same error.
 
We cant find any information about this T_19 Trigger and which fields might be used within our knowledge.
 
Does anyone have a workaround or knows what this trigger does?
 
 
Im looking forward for your help!
 
 
Kind regards
 
Nils

Hi,
I have a problem regarding an issue within the FSL app and especially the cache:

THE SETUP

Every Day we have between 3-5 Service Appointments each with corresponding work orders for a mobile worker. On each of these Work Orders we have related objects such as related Work Order Line items.
We use a Field Service Lightning Flow that allows the mobile worker to "Clock In" or Out of the service. This Flow queries various related objects starting from the work order in order to present the right information.
We work with the latest FSL App on the latest iOS Version
Caching in the FSL Mobile settings are set to:

Record Data Cache Time in Minutes: 15
Metadata Cache Time in Days: 7
Schedule Update Frequency in Minutes:5 
Enable Full Edit on Records: False

THE CHALLENGE

When the mobile worker clicks the lightning button and executes the flow he has only a slim chance that the flow actually gets the correct information. So we swipe down on the work Order Detail screen in order to get the latest info and there's seemingly a 50/50 chance that he actually gets the correct related records into the cache. (looking at the related tab of the work order). When he does get all infos, everything works perfectly.
We would like to be certain that the flow always gets access to these related records without having to constantly swipe down and hope for the best. 

Any input or ideas on why this happens and/or how to fix it are greatly appreciated.

Hi,
I have a problem regarding an issue within the FSL app and especially the cache:

THE SETUP

Every Day we have between 3-5 Service Appointments each with corresponding work orders for a mobile worker. On each of these Work Orders we have related objects such as related Work Order Line items.
We use a Field Service Lightning Flow that allows the mobile worker to "Clock In" or Out of the service. This Flow queries various related objects starting from the work order in order to present the right information.
We work with the latest FSL App on the latest iOS Version
Caching in the FSL Mobile settings are set to:

Record Data Cache Time in Minutes: 15
Metadata Cache Time in Days: 7
Schedule Update Frequency in Minutes:5 
Enable Full Edit on Records: False

THE CHALLENGE

When the mobile worker clicks the lightning button and executes the flow he has only a slim chance that the flow actually gets the correct information. So we swipe down on the work Order Detail screen in order to get the latest info and there's seemingly a 50/50 chance that he actually gets the correct related records into the cache. (looking at the related tab of the work order). When he does get all infos, everything works perfectly.
We would like to be certain that the flow always gets access to these related records without having to constantly swipe down and hope for the best. 

Any input or ideas on why this happens and/or how to fix it are greatly appreciated.

Hi,
I have a problem regarding an issue within the FSL app and especially the cache:

THE SETUP

Every Day we have between 3-5 Service Appointments each with corresponding work orders for a mobile worker. On each of these Work Orders we have related objects such as related Work Order Line items.
We use a Field Service Lightning Flow that allows the mobile worker to "Clock In" or Out of the service. This Flow queries various related objects starting from the work order in order to present the right information.
We work with the latest FSL App on the latest iOS Version
Caching in the FSL Mobile settings are set to:

Record Data Cache Time in Minutes: 15
Metadata Cache Time in Days: 7
Schedule Update Frequency in Minutes:5 
Enable Full Edit on Records: False

THE CHALLENGE

When the mobile worker clicks the lightning button and executes the flow he has only a slim chance that the flow actually gets the correct information. So we swipe down on the work Order Detail screen in order to get the latest info and there's seemingly a 50/50 chance that he actually gets the correct related records into the cache. (looking at the related tab of the work order). When he does get all infos, everything works perfectly.
We would like to be certain that the flow always gets access to these related records without having to constantly swipe down and hope for the best. 

Any input or ideas on why this happens and/or how to fix it are greatly appreciated.