djangodunn37,Here is the way I have gotten it to work to add Staff to Appointments by an external (non Key field) lookup. The part your missing is that you need to setup the field your using as a selector field if its not already for the systems key field. I added Account Ref# in my case as a selector column on the Staff Member ID to get the option to choose the field “Staff Member ID → Account Ref #” If you need help adding a selector see below.Create a Customization project and field the field you need to add a selector on and under attributes pick Customize Attributes. This brings up the field in the Data Access view. Click on. Sellector Columns and then Add Columns and find the field your using to lookup the key field and add it. Then publish and you should be able to pick the selector in the Import Scenario. Let me know if you have any other issues with it. This took a lot of trial and error for me to get figured out as well… -Greg
I’ve been working with Service Management for over a year but we are not using it for Dispatch. We have over 80 field techs using it with the iOS app/Web and its been a long road to get things to a reasonable state with many workarounds… Currently we are using a Rest endpoint to pull the Service Orders / Appointments into Acumatica from our partners SFDC / ServiceMax instance where they are already assigned and scheduled. After that point all activity is captured in Acumatica from Travel to appointment time with Services and nonstock items. I would be more than happy to join a group of others using Service Management to share ideas and best practices.
Already have an account? Login
Enter your username or 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.