The events API doc says that the Product update events will be recorded if a product info is updated. But I only see product create event in the list of events. I don't see any product update events. What could be the reason ? Is it a bug in Shopify API ?
https://help.shopify.com/en/api/reference/events/event#products
Right from the API docs you pointed to:
update product_title was updated. The product was updated.
Not sure how you read that is missing, but it is clearly there.
Related
So Stripe support is currently not able to answer my questions. I have a Wufoo form set up and Stripe subscriptions tied to it. Well I have mapped the product values in the Stripe subscriptions to my form values.
However, I am not looking at an open field for a donation form to let a user define a price. Stripe support can't seem to find an answer. My assumption the support staff is combing their documentation and Google to find an answer and they can't, the same as I have.
That said, does anyone know if you can pass an open value to a Stripe subscription.
In essence letting a donor define the price they want to pay monthly.
So I checked with Wufoo and through them, the answer is no. Not right now. You can not add an open value. I have seen other systems using Stripe in which they allow open values, which means it is possible, but I guess not through Wufoo and you will probably have to write your own subscription code to handle it.
I am trying to detect when a user changes the status of an item in a Podio app. For example: I have an expenses app in Podio. I would like to be notified when the status of an item is changed. The field is a "Category" field type and Let's say the category options are "Pending", "Paid", and "Canceled" I want to be notified only when the "Paid" category value is active
I can see documentation on Podio's API documentation site for how to create a hook if the value of an item is changed "item.update" but how do you go a bit further to specify that a field is updated to a specific value or condition?
The Podio API hook options referenced above can be found here: https://developers.podio.com/doc/hooks
Podio webhooks doesn't support that granular conditions. You can create webhook for item.update which will be fired each time item is modified, you also can create webhook for specific field and it will be fired on any update for that field (so if other fields in item are modified then this webhook won't trigger).
Additionally, the three hooks item.create, item.update and item.delete
can also work on a field level. If you use "app_field" as the ref_type
and an app field_id as the ref_id your hook will only be triggered if
the changes happen to that particular field.
Also, there is different way of achieving similar result. Have a look on Podio workflows: https://help.podio.com/hc/en-us/articles/204366037-Advanced-workflows . Workflow can be configured to be triggered when specific field is set to specific value which is what you were looking for.
I am attempting to work on some integration with Shopify and Shippo, part of the process is sending an email to our warehouse including the order line items with the Shipping Label attached as a PDF.
When we create the label in Shippo, the fulfillment information is updated in Shopify correctly, but I was wondering if there was any way to link the two back up reliably from an API perspective since the Shippo API appears to not include any invoice information. I see a link to an internal order object, but the API docs don't seem to stipulate any further information and the Shopify Fulfillment record does not appear to include any Shippo object id.
The only thing I see if the Shippo Order Metadata field which includes the order number, so I suppose I could parse this and make the request to Shopify's API but I would prefer a more concrete link if one is available.
We (I'm working on Shippo's product team) currently don't officially support Shopify Fulfillments with Shippo API label purchases.
That said, we have an Orders API endpoint in beta. The Orders endpoint allows you to retrieve all Orders of a Shippo account, including those imported automatically from Shopify. Each order, like all other Shippo resources, has an object_id field.
When you create a label through the Shippo API's Transaction endpoint, you can link the Order to the Transaction by sending the additional flag order, setting it to the object_id of the corresponding Order (e.g.: { ... "order": "<order-object-id>" ... }). This will trigger the corresponding Fulfillment of the order on its shopping cart platform, in your case Shopify.
Feel free to reach out to product#goshippo.com if you have more questions about this endpoint. Please keep in mind that it is still in closed beta and the endpoint might change in the future.
I've implemented subscriptions through ReCharge where users can select products and these are saved as line item properties for that product. This was the only solution I could think of with my limited time using Shopify.
Per this question, it seems like line item properties are read-only after checkout. If this is truly the case, is there any solution that enables having modifiable subscriptions where users can re-select products for that subscription product that I can implement?
I'm using Shipstation for the shipping piece if this matters at all.
How can I implement modifiable products (which are subscriptions) in Shopify?
You can't. Well, technically you can but it is not easily done. Since you indicated that you're looking for official answers, I've contacted Shopify via email for you and I've been discussed this with Brad Leclerc, where he said:
That is indeed the case with line item properties being read-only after checkout, so it would need to be reconstructed for the new order. There's no super quick/easy to do that without some custom development to automate the process. If you end up wanting to do that, I'm sure a developer from http://experts.shopify.com could set something like that up.
You have two choices, either hire someone from experts.shopify.com to help or build your own marketing script from scratch.
Proof of email: http://i.imgur.com/OeM5gSm.png
I'd do this with meta fields on the customer.
meta fields can be used on the subscription product template to make it sensitive to the state of the customer's subscription (new or existing)
Use a order web hook to detect when a new subscription product has been purchased and then update the customer meta fields (e.g. subscription level and start and end dates).
use a periodic task in your supporting private app to:
prompt user before subscription becomes due to update their payment details or cancel the subscription
create and bill new orders for each subscription period
I am not familiar with Shopify, nor Revcharge, but according to the references, couldn't you simply customize the product page in shopify?
https://docs.shopify.com/manual/configuration/store-customization/page-specific/product-page/get-customization-information-for-products
According RevCharge, you should use a Shopify product template anyway..
http://recharge.helpscoutdocs.com/article/91-recharge-integration-guide
Before I ask my question I want to give you a quick overview about the topic.
I got a sharepoint list (SP 2013) which has content approval feature enabled. For this list you can choose who should see the draft versions of an item. Most logic option here is to let the author and all approvers see the draft. Now imagine that an item has been approved and now again edited. There is a version that is draft (because it needs to be approved again) and a version that had been approved before.
Here comes the tricky part :-). I fetch the items of that list via REST api. My query includes "_ModerationStatus eq 0" which means that I only fetch approved items. Users who are not allowed to see drafts automatically get the last-approved version of the item, although there is a draft version waiting to be approved. Users who are allowed to see draft versions see (I would expect something different here) NOTHING! So instead of fetching the last-approved item, the query has no result for users which are able to see drafts. Now if I perform the query without "_ModerationStatus eq 0" these users see the draft version while others (not allowed to see drafts) still see the last-approved version.
So finally my question is: Is there any chance to change this beaviour? I want SP to return the last approved version for ALL users via REST api. If these users open the SP-list itself they sure should see the draft. So it is only about the rest api.
I don´t think that this is possible (did not find anything to change this) and I thik the REST api just mirrors the behaviour of the native view behaviour of the SP-list-view itself.
Thank you in advance!
regards
Ben
Here are two possible solutions for this problem:
Create a second list and let a workflow create or update items on this list whenever a new or updated item has been approved on the main list.
A: Worklist -> New or changed Item -> Workflow -> Create or update item on List B: Productionlist
Use the unique ID of items to check if an item does already exist on list B.
You can read about the second possible solution here: https://sharepoint.stackexchange.com/questions/116921/distinguish-between-approved-and-not-approved-items-rest-api
With OData__ModerationStatus it is possible to get the approval status for each item that your request fetched via REST. So you could probably place a flag DRAFT to any not approved draft versions to let the author and all approvers know that this is not an approved version.
Of course it is possible to get the last approved versions for each item but that will cause a need for additional requests and validation etc.
Hope this helps :)
Just use the following,
http://WebAppUrl/_api/web/getfilebyserverrelativeurl('/RelativePathToFile')/MajorVersion
Example:
http://contoso.com/_api/web/getfilebyserverrelativeurl('/_catalogs/masterpage/css/main.css')/MajorVersion
That returns the recent major version published