I see an ambiguous content in the snowflake documentation. In the guide, https://docs.snowflake.com/guides-overview-sharing#options-for-sharing, it says all listings use auto cloud fulfillment. But then in the link https://other-docs.snowflake.com/en/collaboration/provider-listings-managing.html#managing-consumer-listing-requests, it says that not all listings are auto cloud fulfilment. Only private listing and paid listings are auto cloud fulfilled.
Can anyone please clarify which of these about listings is true
All listings (except personalized listings) can use auto-fulfillment. Private and paid listings are required to use auto-fulfillment for cross-region fulfillment.
Thanks for this feedback - the team is now aware that the docs need this improvement.
Related
We have a java client for downloading orders from Amazon MWS.
We use:
MaWSJavaClientLibrary-1.1.jar
MWSClientJavaRuntime-1.0.jar
MWSOrders_2013-09-01_v2020-10-20.jar
We download an xml with users data, with also shipping details (address, city, zipcode and so on...)
Begining from half 2020, we didn't receive customer name and address anymore. I mean that those 2 tags in xml were not passed anymore. We realized that something was changed in Amazon MWS for GDPR and security reasons.
We compiled a form online where we sent to amazon lots of informations about how we use those data.
However, we have not understand what we have to do in order to get those data again in xml.
Our client continues to work as usual, beu we continue to get xml without customer name and address.
Last email from amazon says:
Good morning,
thank you for your reply. As this issue is unrelated to your Developer Profile role assignments, we recommend that you review the information available in the links below for information on this topic.
Since the new API for Sales Partners (SP-API) is officially available, we are no longer issuing new credentials for MWS and are not updating existing MWS access roles. From now on, it is possible to develop applications in multiple regions with a single set of SP-API credentials.
More information on SP-API can be found here:
https://developer.amazonservices.it
SP-API documentation on GitHub: https://github.com/amzn/selling-partner-api-docs
If you still need assistance on this topic, you can submit a MWS or SP-API technical support request here: https://developer.amazonservices.it/gp/mws/contactus.html
Thank you for selling with Amazon.
is there anyone that had same problem and can help us to retrieve those information again please?
Thanks
I am currently trying to follow the steps listed here:
https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-authenticate-an-ews-application-by-using-oauth
However to add the delegated permission I need (EWS.AccessAsUser.All), the author suggests you should
"Select Add a permission. On the Request API permissions page, select Exchange under Supported legacy APIs."
This worked a few months back when I tried it in a prototype but the whole Exchange API under the "Legacy APIs" section appears to have been removed.
I can not find any mention of this anywhere on GitHub, SO or MSDN.
Please note some of the functionality I need is not yet supported in Microsoft Graph so using that API is not currently an option for me.
Any help would be appreciated.
I found out to my surprise that now you will need to search it within the "APIs my organization uses" by the name : Office 365 Exchange Online. You will be able to assign the necessary permission afterwards.
I've posted this question on the Amazon Developer Forums but I'm not getting a response. In the meantime, I thought I'd see if any devs on here can provide any insight or advice:
I’m building an Alexa skill for a client. So far we’ve added the following features to skill and they are successful:
Add items to user Todo List
Add items to user Shopping List
Get permission from user to use Amazon Pay.
We need to be able to give the user the option to add an item to their Amazon basket/cart from the client’s existing Amazon store. I’ve read all the posts/answers related to this issue on the developer forum and all of them were published last year.
The answers I’ve read seem to suggest we can’t add an item to a users Amazon basket/cart.
Is there an update on this for 2019? Can we do this with Amazon Pay or the Account Linking feature?
If not, is it technically possible if we build a custom back-end to work with the skill?
Any help would be greatly appreciated.
Many thanks.
assuming you are creating custom skill with ASK. Yes, you can add the product in the cart using Amazon Product Advertising API Please refer blow documentation link for more information. you can do lots of other stuff like modify the cart, adding wishlist, remove the product in the cart. https://docs.aws.amazon.com/AWSECommerceService/latest/DG/AddingItemstoaCart.html
Hope this helps.
.
I created a Gmail account for development and enabled the APIs for developer console. I generated one API key which I used in my application but now I forgot the Id that I used. I have to upgrade the plan for APIs but for this, I need the Gmail Id. Is there any way I can get the Id?
Ok, So after I have tried different options I was standing in the same position. So I dig all into my accounts and luckily my recovery email id was one of them, so I searched for all the emails from Google having the subject as Security your linked Google Account and sender as no-reply#accounts.google.com this will give you all the Ids associated with it.
The only workaround to fix the issue is to contact "Google API support team"
Just Go to the given link and raise your issue. They will assist you further steps to follow. https://support.google.com/googleapi/?hl=en#topic=7014522
I hope this will help you :)
We are submitting an Outlook add-in app to the Office Store. Our add-in has a "Help" link in it that points to our customer care / support site. However, our support site does require a log in...our customers need to log in to search knowledge base, log a support case, etc. We have no way around the fact that our support site requires log in...this is just how our support mechanism works. So, we are getting the following comment with our rejected submission: "The current Support URL in your add-in metadata, as submitted via the Seller Dashboard, requires authentication. Please use a Support URL that is publicly available."
Has anyone come across this? If we don't have a publicly available URL for our support site, that doesn't require login, what other options do we have?
The support link submitted with your add-in metadata, is the link that will appear on the Office Store on your add-in listing as the "Provider's Website".
This link does not have to be a link to your support site; but can be a link to your main website.
Hope this helps!
You can create a public facing support site with simple text stating that support is paid/requires credentials and provide a link to the protected URL. For all unpaid/free trial users, you can list an email address within the same text.