Search
-
Michael - it appears that the contacts issue is more serious than
thought. We now have two customer contacts who have been inserted into our
Employee table - one superimposed on top of the existing values for a current
employee, and one contact who's now listed as an entirely brand new employee,
linked to another.
What ...
-
Well, that's the story of *my* life... standing by.
-
Suddenly I'm getting very weird behavior in the Add/Edit All Contacts screen - the screen is repeating contacts from Customer to Customer record. (As in, a contact for Customer D is showing up as a contact for Customer R.) I can't tell if I'm having a refresh problem, or if my database is hosed.
Anyone else having this issue?
-
Unfortunately, not all of my Sales Reps are Employees - some are Vendors, some are in Other Names. I've confirmed phone # and email addresses for the Employees and Vendors, but the Other Names list doesn't provide for those fields. What's next?
Also, I really need to actually understand how this linked fields function works, and what ...
-
Well, *that* was embarassing... you were right, the Sales Rep table didn't have phone and email values where I was expecting them. I exported the Sales Rep table and updated it, but now when I try to re-import, a strange thing happens: I can't select "Phone" as one of the Existing Fields for that column, because "Phone" ...
-
We had to rebuild our QB file yesterday after having login issues. At least one Changes synch completed after the rebuild (12:18 pm) and we shut down the Method engine at that point so that it wouldn't impair QB performance on that system. We restarted Method at approximately 5:00 pm, but at some point after 6:00 pm (the last time it was ...
-
Use the path:
Sales Center | Contact Activity | Send Email | Use Template: General Follow-up
I didn't see your linked field in the Customer table; did you delete it after you tested it?
-
Michael - it appears that you have to give the new linked field a name that's unique from left-to-right: when the merge command is parsing the field name it stops as soon as it "reads" an existing field name. To illustrate:
Customer.RepName - works
Customer.SalesRepName -- merges out to ...
-
I know this error has been logged - I'm just noting that I tried again, and got the error when attempting to click Finished. I was able to refresh the screen and return to the Edit Screens list of screens, and when I checked the Customers screen again, the new linked field was listed... but it's still not working in the email, and I ...
-
I think the bug or whatever that popped up prevented the definition of the linked field. When I use the email template now, I get:
{Value of Customer.SalesRep} "Name"
Which displays as, for example:
"TO Name"
because for this record, "TO" is the value of Customer.SalesRep, and "Name" appears to be the ...
|
|
|