We created a composite field, analogous to the baseline address.full_address field. However, it does not appear on the object.In Custom metadata: Selecting (for example) the column in a hierarchy_select gives an error:<message>Table request_contact does not contain a column with name full_name as specified in the query.</message>What are we overlooking?
We currently have a integration map to process incoming data from a middleware solution. When we call the ODATA endpoint '/perform_inbound_integration', and provide the information in the middleware terminology, it gets translated and processed correctly.We want to retrieve the information via ODATA via the same integration map, so also translated to the middleware terminology. How can we retrieve this mapped response? I am not looking to trigger an outbound perform, as this then should login to another endpoint, making things way more complex.For example:The integration map contains these mappings. We can POST to /perform_inbound_integration with this data"parameters": { "mapping_name": "our-odata-middleware-test", "xml_import": { "inbound": { "ticket": { "description": "test-ticket", "priority": "P1", "category": "outdoor", "created": "2022-01-18T12:26:19.000+0100", } } }}How can we GET from some ODATA endpoint and retrieve something like"ticket": { "description":
Hi all,Is there a way to control the ordering of the layers in the schedule board? Our calendar exceptions are often obscured by the standard shift, making scheduling errors very likely. The ordering now changes from time to time, from load to load, and from scroll position to scroll position.How can this be controlled / configured? We're currently working on version 6, update 12The standard shift (grey) overlapping and obscuring the calendar exception (orange)
In FSM Mobile 6.4, when you add a new screen, you choose a workflow. It will only appear in this workflow and not be available in other workflows. If you choose no workflow, it's visible nowhere.We have several Debrief workflows, depending on the task_type at hand. How can we add a screen and use it in multiple workflows, to improve maintainability?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
