Free field z_internal_string_1

Hi Laurence,

I am not sure that the column service_call_env.z_internal_string_1 is used or not in any of the code (I am asking around) but I don’t understand why you would not use Customizer and create your own field?

Please explain what led you to this decision to try using the z_internal_string_1?

Hi Phil,

We need to update a field that we can use to re-dispatch on mobile when updated.

So we need a field that we can use in the Workflow (mobile) parameters, and We’re not sure a custom field is OK for that.

Thank you

Hi Laurence,

I still am not sure why you don’t use a Customizer field and then specify that database column from the header.  I don’t believe using the service_call_env will trigger a dispatch as the options are for Alliance Header Fields (order_line) and Activity Fields (where demand.bpart_gcl_id = Labor or demand_labor fields...)

I probably would consider using Customizer to update a field created as toggle but the problem with either your solution or mine is what is going to set the field back to the state where it should not dispatch?  That is logic and may require some backend programming.   Thus customization.

What most of our customers do is modify something simple like the problem description adding a space or some character to trigger the field has been modified instead of trying to use a field that would have to be reset again after the dispatch to reset it for the next time.

Alternatively, you could just go to the Assign/Dispatch page, Exclude from Mobile, Save and then revert to redispatch.