Method Community

May 25th, 2015 Contacts App Updated App Description Removed App Ribbon from Edit Entity Screen (Ticket AS-769) *New* Added ability to add / edit Lead Source (Ticket AS-442) Activities App Updated App Description Corrected criteria used for verifying required fields when creating a new follow-up activity from the New Activity ...

May 13th, 2015 Invoices App Fixed issue related to permissions on New / Edit Invoice screen

The following updates are now live for users of Method:Classic.  Fix - Sign up for QBD account on Method:Classic does not display first & last name on profile page (Ticket PL-668) Fix - Unable to use the Send / Resend invitation email button from the User Setting page (Ticket AS-610) Cheers, Jonathan

Hi rgatton, Thank you for bringing this issue to light - This is not expected behaviour.  I've confirmed that this is happening when creating a Credit Memo from the Method front end as well.  I have created a ticket with our development team to investigate this issue and will post back once I have any updates. Cheers Jonathan

Mark The issue here is that the API does not support Cross Tenancy in the case where the same drop down value exists in multiple tenants. When you are inserting into Tenant A, the API will utilize the drop down value from Tenant A.   I will create a feature request for an update to this logic - but I do not expect to see ...

Mark - Is the insert into the Invoice Line table cross tenancy ... Meaning, are you logging into the API using Tenant A, but inserting the record into Tenant B? Or is it the case where you are logging into the API using Tenant A, inserting the record into Tenant A, but the record is being assigned a dropdown value that exists from ...

Sorry for the inconvenience here, Mark.   I will create a ticket for our development team to investigate this issue and will keep you posted with any updates via this thread.  Unfortunately I do not have a work around for you at this point in time using the API.

Hi LaCrews, Your assumption is correct.  We have experienced this when using the Insert Record Into Table action on the front end.  To overcome this on the front end, you can insert a RecordID into the field name of a drop down as long as the value is stored within an Action Result.   As Mentioned in the previous post I just ...

Hi LaCrews, Ok - Are you successful if you insert into the Field name directly?  I'll have to followup on further on my end to verify this feature.

Hi Raghuveer, I have several follow up questions for you: Are you trying to create Customer or Customer Lead records via the API? Within your alternate account, is the Lead Tab customized, or a default Method screen? If you are trying to create Customer Lead records using the API, you will need to include an additional field when ...