Search
-
Hi Rolf,
FYI – please see a post (click here) that provides more details when customizing fonts in the Method Report Designer. Thanks.
-
Wonderful, thank you for the comments!
-
I'm using the Report Designer to print cheques, and am having a problem with the MICR font used for the cheque encoding. It works fine in the designer, but when I generate the report in method, it uses some other font to create graphics in place of the MICR symbols in the PDF file. Any thoughts on what the problem might ...
-
Hi Dominic Riccetti,
You cannot run actions in the API. So if actions are being used to populate something like an action result in the UI, and then that action result is used in the send email action, you cannot do that via the API. The MethodAPIActionSendMail function takes in the parameters specified and sends an email.
However the ...
-
Hello,
thank you for the reply, I assume then I can do every action from the MethodAPIActionSendMail that we can in the UI to mock the users action?
Thanks,
Dominic
-
Hi there,
My suggestion is to have them log in as Method users. This would provide you with more off the shelf features, more robust and flexible options in the future.
As you start to ad your Method users to your account (Customize>>>Users) you can set up the sharing between them in step 6 of the wizard when you edit each user. We ...
-
I guess what I"m looking for is to be told what would work best for us. We're brand new to Method, you see.
In Quickbooks, we have, oh, around 8 or so customers, each with 1 to 1000 jobs. Quickbooks deals with this correctly; Method does not seem to. It sees 3000+ individual customers, which happen to have the ...
-
Hi Bryan,
In step 8 of setting up a user, you can grant/allow access to tables for the user. Then they can only see the data in the allowed tables
Dave
-
Hi LaCrews,
That is correct, whatever tables you allow in step 8 of setting up a user are the tables they can interact with via the API.
Dave
-
Hi Dominic Riccetti,
No you cannot.
I will put a suggestion in with the dev team, about adding this to a future release of the API
Dave
|
|
|