Search results by user ID 35416

Re: Using MethodAPIGetScreenURLV2 to get URL to view contact

devonbondi — Fri, 14 Feb 2020 14:26:50 GMT

I agree,

It was a nightmare working with this. The documentation was horrible and then having API calls that are avaiable with abousolutely no documentation was unreal... I honestly couldnt believe it - coming from an established CRM company - this is completely unacceptable.

And the task that we were trying to perform was a very common one, it shouldn't have been such a task to get it to work.

I like the CRM - in most other aspects it was very good - but the API and it's related support needs much work. You cannot have undocumented API calls, its unacceptable. That makes the API call completely useless. And asking a developer to completely guess at (several!!) open-text parameter values is completely unacceptable, as our chances of guessing the correct values that your system is expecting is almost 0%. If you have a parameter that is expecting a certain value - you MUST LIST ALL VALUES THAT PARAMETER IS EXPECTING IN THE DOCUMENTATION - you cannot tell the developer to just guess!!! Thats insane!!

I will never take a job that deals with the methodCRM API again - it was a complete nightmare. My best wishes to any other developers who venture to work with this api... good luck!

PS - You cannot try to charge companies for support of your API when your documentation is incompleted and call it extra development work. It's not extra - its just making up for the fact that you were lazy in the first place and didnt document your API correctly, and then when a developer needs to use said API calls, you cannot then charge them for asking questions because there is no documentation. Thats a great way to lose customers and developers.

I hope you guys change this problem quickly - because otherwise your system was very good. I liked working with it other than the API. If you cannot document it correctly - then kill it until you can. Because otherwise your just hurting yourselves.

Best of luck!

Re: Using MethodAPIGetScreenURLV2 to get URL to view contact

devonbondi — Mon, 20 Jan 2020 20:34:13 GMT

Thank you.

How about MethodAPIGetScreenURLV3 or MethodAPIGetScreenURLV4? Do those work to generate a URL for the new version of method?

The version 3 and version 4 of the call also have TabName and TabLinkName parameters... And those parameters appear to be the only way to tell the system what screen your trying to get a URL for.

I've listed my use case in the post, basically just trying to get a URL for the view screen of a contact. How would I do that ? Is the getURL function still supported? I know there is v3 and v4, but again both of those still have TabName and TabLinkName parameters so I'm a bit confused.

Please let me know how I can accomplish getting a URL for an individual contact.

Thanks!

Using MethodAPIGetScreenURLV2 to get URL to view contact

devonbondi — Fri, 17 Jan 2020 21:48:04 GMT

Hello,

I'm trying to use MethodAPIGetScreenURLV2 call to generate a MethodCRM URL to view a specific contact.

I'm having difficulty with the call. I can get it to successfully send the call, however, it either fails due to TabLinkName & TabName not being valid or in the one case I've gotten it to work (based on examples i've seen online) and return an actual success response, the URL has been empty.

Can someone please help me with this. My task should be fairly simple. All I want to do is be able to generate a method URL that will open to a specific contact record in the viewing state.

My problem is, I have no idea what exactly to put for the TabLinkName and TabName parameters. I have no idea where to find them. The one video I found seems to deal with the "Classic" version of method since the interface is completely different.

So again - if someone could help me with what the exact parameter values for strTabLinkName and strTabName should be to open a contact record in the "view" state - that would be greatly appreciated!

Thank you!

Devon