There is a POS windows application where a store manager processes bills for customers. Our client want us to provide them an API service where this service will add a customer as a contact and also be assigned to a POS contacts contact group in Kentico 12.
Is there any possibility to achieve this using Kentico 12 Rest API out of the box feature?
In Kentico contact membership in a contact group is stored in om.contactgroupmembercontact object type. So I believe the following should work:
POST request to URL: ~/rest/om.contactgroupmembercontact?format=json
And the following data:
{
"ContactGroupMemberContactGroupID":yourContactGroupID,
"ContactGroupMemberType":0,
"ContactGroupMemberRelatedID":yourContactID,
"ContactGroupMemberFromManual":true // Manually added contact
}
You need to know ContactGroupID and ContactID which can be retrieved with other queries.
Related
I'm currently building an integration with Netsuite using the Suitetalk REST API. I would like to retrieve the role of each contact associated with a customer to find the Primary and Operational contacts of the customer.
I have tried querying the customer endpoint:
record/v1/customer/ {customerId} /contact/ {contactId} /contactrole
This query returns Role id 14 which is 'Customer Center' for all customer contact records. This is obviously incorrect as this information is returned for contacts tagged with different roles when I check them via the UI.
I have also tried using Suiteql using the query endpoint with the similar results.
Is the query incorrect or should I be using a different endpoint? I have been stuck for days, so I would appreciate any suggestion.
A long comment. Hopefully it helps focus your search for a solution.
Contact Roles is the subrecord for contacts who have login access to a customer's account. The role listed there is the access role. Customer Center is the default access role in a vanilla Netsuite account.
The Records Catalog has contactList as the joining table for contact to company. I don't see any mention of role there that would correspond to contactrole in the records browser so it appears some documenation is missing.
You'll likely have to play with the SuiteQL queries feature to get this.
See Executing SuiteQL Queries Through REST Web Services in the NS help.
with suiteql you can get primary contact with this
{ "q": "select cus.companyname,cus.contact,cont.entityid from customer cus left outer join contact cont on cus.contact=cont.id where cus.id=<<id of ur customer>>"}
I have an enterprise app used to send claims to an on-prem ADFS.
I need to send the group names my Guest users belong to. I know that OOTB you can only send the Gpoup ID.
As suggested in other posts I can use the Graph API to get the group name, but how can I then send this as claim?
Unfortunately, it's only possible to get the object ids as of right now. This may be implemented in the future, however, in order to get the group names you will need to have some sort of service that makes calls to the Microsoft graph utilizing the ID.
Please raise the UserVoice or vote for similar uservoice
Want to know the Acumatica REST API to be used to get Account Inquiry / Customer Open Balances. If no such web services then how to extend end point using which modules of acumatica erp
Not sure exactly what information yo are looking for but maybe the following screens could contain it :
Account Summary (GL401000)
Account Detail (GL404000)
Customer Summary (AR401000)
Customer Detail (AR402000)
Though only one of these screen is already mapped in the Default endpoint of version 18.200.001 (Account Summary -> AccountSummaryInquiry)
If you need information from the other screen, you will need to either create a custom endpoint or extend the default one (I recommend extending).
Here is information on how to do both:
Creating a new endpoint, it also contain information on how to add new entities in an endpoint : https://help-2019r1.acumatica.com/(W(14))/Wiki/ShowWiki.aspx?pageid=709351cc-566a-47b3-b153-3a9fdd690ce0
Extending an endpoint : https://help-2019r1.acumatica.com/(W(13))/Wiki/ShowWiki.aspx?pageid=c450492e-06fe-4563-95c3-efa76975415b
I recommend that you take a look at the way the AccountSummaryInquiry entity is defined and follow the same way to create the other screens if this is what you do. I mean by that that you put the parameter of the inquiry in the top level entity and the fields of the grid in a detail type sub entity.
And in order to retrieve the information properly I recommend that you use a PUT request instead of a GET as this is the proper way to do so as mentioned in the following article:
https://help-2019r1.acumatica.com/(W(12))/Help?ScreenId=ShowWiki&pageid=6340cff3-4732-4231-9e42-5d1e5e65b5dd
I have some doubts regarding the custom connector we are trying to build for docusign : -
Regarding the license plan that need to be bought by the customers who will be granting access for our connector to collect data from their docusign organization account. I am looking at the link https://www.docusign.com/products-and-pricing. API access support is mentioned in only the advanced solution. So I was wondering whether only we need to have "Advanced solutions plan with APIs support" plan or all our customers need to API access support in order to fetch their data.
As per the documentation, to make the REST API calls we need two fields 'base_uri' and 'account_id' (https://developers.docusign.com/esign-rest-api/guides/authentication/user-info-endpoints). Now, the response of userInfo API call gives an array of accounts and its respective fields. My doubt is, if multiple authenticated users (more than one accounts) are returned in this array but all are part of same organization, will they all have different account_ids. Main concern here is, will there be several Base Paths (https://developers.docusign.com/esign-rest-api/guides/authentication/user-info-endpoints#form-your-base-path) to make API calls?
2a. Further question is, what is the significance of 'is_default' field?
Is this related to main account (if is_default is true) using which we will create our Base Path?
Since this is a tech/engineering forum I'm going to answer only question #2 as question #1 is more of a business/sales question.
The reason you may get multiple accounts is that an authenticated user in DocuSign can be a member of multiple accounts. That said, it's the same user. Meaning, say foobar#blah.com has an account 123 with company X and account 456 with his school, then it's possible that when foobar#blah.com authenticates (With the same password!) to DocuSign we have a list of accounts associated with that user. We give you all of them when you make the API call. The default one is the main one that you would see when you log into our web app. You can decide yourself as the user which one is the default. Users who log into our web-app then see an option at the top-right to change accounts.
and yes, every API call is associated with a specific account. So when you construct the urls for your API - you do need to know which account for this user you are making the API call for. Your application can decide how to handle this.
Hope this helps.
I am accessing the Netsuite using RESTlet by Oauth token. I could get a contact, customer, and other details. Now I want to get profile [acccount holder] details like my first name, last name, mail id, role, and so on.
What is the record type should i use to get above mentioned details?
Or what alternate code should use to get the details?
It depends on type of user, mostly you would need to query
employee
, it has all the details. when querying/searching you may want to add filter that ['giveacess', 'is', 'T'] as you only want to query users with login access.
Other types of users can be customers, partners and vendors
These users can have access to their portals, eg: customer has access to customer portal, vendor to vendor portal and partner to partner portal.
For details on fields available to query , I suggest you to check record browser link