I am trying to access the "relationships" additional fields in google contacts via the apps script interface. The docs show the "getCustomFields()" call, but it does not seem to contain any information from my contacts about spouse, child, or other relationships.
Anyone know, is there a separate call for accessing this data? I don't see one in the docs:
https://developers.google.com/apps-script/reference/contacts/contact
Related
I have a use case where I want to connect two different user roles, and if they accept and want to connect, new features will open up. It is very similar to how friend requests work at Facebook or LinkedIn, opening up and showing more content. Let's call them role1 and role2.
All users are stored within a "users" collection with an id. Depending on their provided role within the document attached to the "users" collection, they can store additional data in their respective role-collection, i.e., role1 collection or role2 collection.
What is the best approach and structure to connect the two users, i.e., become "friends"? Should I have the connection stored in a new collection, named perhaps connections-collection, or multiple collections?
I'm using Next.js, NextAuth for user authentication, and FaunaDB as a database. I'm using Fauna's query language, FQL.
Have you perhaps seen fireship's video RE: fauna db? I think it covers what you want to do and how you can proceed.
Edit: There are many ways to implement this. Based on my understanding, perhaps you can have "Friends" and "Requests" arrays stored under a user document. That way you can differentiate between confirmed friends or a just request.
Example: When user1 initiates a friend request with user2, you store user1's ref under "Requests" of user2's document. When user2 confirms, you move user1's ref to the "Friends" array.
This is just a overly simplified idea and you may need to consider your options and the implications. You would need to plan and define the predicate in both roles so you would only see what is necessary.
I've been wondering which field should I use when collecting user purchases, views, etc. There are a couple of different resources in Salesforce about this and both of them tell differently.
First one is under Email Recommendations -> Implementation, inside marketing cloud itself:
And it says that Subscriber Key should be used.
The other one is from Salesforce Docs (https://help.salesforce.com/s/articleView?id=sf.mc_ctc_set_user_info.htm&type=5):
This one says that Subscriber ID should be used.
As far as I understand it, these two are completely different. I use Contact Id from Salesforce as my SubscriberKey and I think Subscriber Id is generated inside marketing cloud itself.
The JSON itself has a field that's named "email" - the name suggests that email should be used.
I am using AWS Amplify as the backend for my react app. My application uses Amplify Auth and API.
My project has a model called "Projects" that have a one-one relationship with another model called "Companies". Every Cognito User has a custom user attribute of 'CompanyID'.
When the user is logged in, I want to make an API.graphql request to list all projects related to the company that the Cognito User is assigned to. I am having a hard time figuring out how to filter the query so that it only returns the projects that are related to the specified company.
Is there a way to filter a ListProjects query by passing in the id of the related companies I am wanting to filter by?
I figured out what I needed to do. The problem was that I made the parent "Projects" when it should have been "Company". By making the parent "Company", I get a singular companyID field inside each project file. This allows me to quickly filter by projects matching the assigned ID.
I am creating a web app on MEAN stack and for some reason i have to save two different schema in same collection named "users" and saved the userSchema and customerSchema in that collection in mongoose but in view model while listing the data in user list it shows users as well as customers which is saved in the collection. I want to display users list in and customers list in separate pages.
Can anyone guide me for this problem ??
Thank you in advance!
You have two options: you can either separate the server side queries and have two API calls, or you can use an angular filter (ng-filter) to display only one type in your table. If you're primarily going to be displaying only one type of user per page, I would suggest separating on the server side, to reduce the data transferred to the client, and to allow for improved security (for example if details of one type of user should not be publicly visible)
I'd like to be able to tag affiliate links with some extra information so that I can map successes to information inside of my system.
Is there any way I can include a custom identifier or payload of data with the affiliate link that Amazon will allow me to inspect when I receive a report of successful sales?
The only thing I found is the tracking ids from
Manage Your Tracking IDs page.
However this ids are limited to 100 values by default (you need to contact amazon for more). This is what they answered me:
I understand you'd like to view reporting within Products Advertising
API.
All reports are housed on your Associates account for you to view the
activity of your links.
We do offer multiple tracking IDs so that Associates can track the
activity of individual links easily and accurately.
You can create up to 100 tracking IDs in your account by visiting the
Account Settings section of Associates Central. You'll find a link in
the Account Information section labeled Manage your tracking IDs:
https://affiliate-program.amazon.com/gp/associates/network/your-account/manage-t...
Once you've created your additional tracking IDs, to view these IDs,
please log into Associates Central (http://associates.amazon.com).
Once logged in, click on the drop down box under Tracking ID to change
which ID you are working with.
If you are interested in receiving more than 100 tracking IDs, please
first create this amount via your associate account in Associate
Central. If you have already created 100 tracking IDs in your account
and are needing additional tracking IDs, please use the link below to
write back to us with a detailed description of how you'll be using
these additional ID: