Add current dateTime to function input query #416
Replies: 6 comments 26 replies
-
|
Getting the exact time is critical to some custom logic and is an absolutely necessary feature. Example: Time the function needs to be active can be set to a half an hour or 45 minutes, due to store special offer campaign. Currently that is not possible to control. |
Beta Was this translation helpful? Give feedback.
-
|
@nickwesselman are you imagining two variables in a JSON metafield like this passed into their function? Metafield JSON value
Input query |
Beta Was this translation helpful? Give feedback.
-
|
Yep exactly. |
Beta Was this translation helpful? Give feedback.
-
|
Or even better, https://shopify.dev/docs/api/functions/reference/product-discounts/graphql/common-objects/localtime |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for suggestions, but there could be infinite time constraints. I am reusing cart-transform function for multiple campaigns. Each campaign can set its own date time settings. So it is not possible to define every set of timeStart and timeEnd in json and process in graphql query, without knowing the exact number of variables coming. I could predefine 10 or 20 variables ($promoTimeStart_X), but number of campaigns can go above 20. Although it works, that would be a bit of limitation. |
Beta Was this translation helpful? Give feedback.
-
|
Our long-term recommended approach for this would probably be to separate the campaigns into multiple transforms / function instances. There are restrictions on the number of them at the moment, but we aim to expand this in the future. |
Beta Was this translation helpful? Give feedback.
-
Is there a reason you can't use input query variables for this? |
Beta Was this translation helpful? Give feedback.
-
|
@nishikawa-nobuyuki Thanks for the use case description. It's not ideal but a workaround would be to put the product ID and availability time on a metafield on the validation object instead. |
Beta Was this translation helpful? Give feedback.
-
|
I also need to use a current-time object in similar case here. I understand that executing the function, which compares two different date-time objects , in the shopify backend and pass the result to our custom app is fast and accurate. If shopify really don't want us to have a datetime object inside a validation function, it would be nice if we could execute dateTimeAfter function via api within validation function. I really hope it will be possible for us to implement this type of validation soon. |
Beta Was this translation helpful? Give feedback.
-
|
@nickwesselman Hey Nick, I'm OK with implementing the workaround you mentioned using metafields (storing some date in a metafield) and then evaluate if that time has passed or not in our Shopify Function. However, my only worry is that I store the time along with a timezone in the metafield and I evaluate against it - what happens if there is a change in the stores timezone? The metafield value holding timezone becomes outdated and no longer accurate. I'm wondering if there's any way to combat this by directly querying the stores timezone somehow within the function? I couldn't see any in the offical docs around getting the timezone of the store specifically: https://shopify.dev/docs/api/functions/reference/cart-checkout-validation/graphql/common-objects/localtime Basically, I want my function to "activate" a field at the same time as every other function user (timezone agnostic) and to do this, I'd need to know the timezone of the shop. |
Beta Was this translation helpful? Give feedback.
-
I have thought about moving the configuration of a launch date into our app where the information is written to the function to read as query input variables. As soon as there is more than one product to validate though, this solution is not sufficient, is it? |
Beta Was this translation helpful? Give feedback.
-
|
@timfuhrmann You could use multiple, separate validations in this case |
Beta Was this translation helpful? Give feedback.
-
|
+1 on this. Have a need to be able to block checkout if items were added to cart more than X minutes ago. In the majority of cases X will be a short time-frame such as 15-30 minutes. Idea would be to:
|
Beta Was this translation helpful? Give feedback.
-
|
I really need this solution. In my case, some cart line items need to be deleted or prevented from checkout 72 hours after being added to the cart. |
Beta Was this translation helpful? Give feedback.
-
|
+1 exact same on my end... |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
hey @nickwesselman and team- Running into an issue with localTime. I've removed the variables I was passing in the Input to isolate the problem as much as possible. My super contrived input looks like this: All of the hourN's evaluate to false when the function runs: any thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @abaileyb -- Sorry to redirect but we don't provide support via this discussion board. Could you post to the community forums? |
Beta Was this translation helpful? Give feedback.
-
|
+1 🙏 This would be really useful when you need to compare time with a line-items attribute |
Beta Was this translation helpful? Give feedback.
-
|
Adding another use case here as I think this is a very important feature that is definitely needed within the community. Products can be placed on a 24 hour hold by customers. A timestamp is added to a product metafield of when that hold expires. If the hold date is lower than the current date, the hold is expired and the checkout/cart should be invalid. This is the current structure of the Cart validation function input using version 2025-1 of the API: query RunInput {
cart {
lines {
merchandise {
... on ProductVariant {
product {
hold_date: metafield(namespace:"hold", key: "date") {
value
}
}
}
}
}
}
shop {
localTime {
date
has_expired_hold_future_date: dateTimeAfter(dateTime: "2025-02-28T12:00:00") # returns false
has_expired_hold_past_date: dateTimeAfter(dateTime: "2025-02-24T12:00:00") # returns true
}
}
}The dateTimeAfter and dateTimeBefore functions won't work for our use case, as these require the DateTime being hardcoded within the function input. We need to be able to use the DateTime stored in the product metafield. Our ideal scenario for this would be if Shopify is able to add the DateTime into the LocalTime Object. That way, we can perform the check within the Function logic. shop {
localTime {
date
dateTime
}
}Outputs {
shop: {
localTime: {
date: "2025-02-25",
dateTime: "2025-02-25T12:00:00"
}
}
} |
Beta Was this translation helpful? Give feedback.
-
#215 shipped date and comparisons, but no dateTime. @nickwesselman mentioned this is due to function run caching.
We need (and others report needing) the current dateTime. Here's our use-case:
specifiedDeliveryDate.specifiedDeliveryDate.Actual behavior
There is no
dateTime, onlydate, nor do any comparison functions work to compare the current dateTime to a variable. It currently only allows comparison to a metafield value, but we can't update a metafield value to be the 8:00 pm the day before the Cart attribute'sspecifiedDeliveryDate.To solve my use-case, I did a workaround using a combination of
dateandtimeAfterbut had to hardcode the cutoff time. Eventually, we'll want to have different cutoff times per delivery day and doing a dynamic cutoff of hour granularity would get a bit hairy as you'd have to add 24afterX...fields.Expected behavior
Shopify adds a
dateTimefield toLocalTimethat can be used in validations in a function run (e.g. compare it against a Cart attribute or Shop metafield that holds a hash like{ "2024-01-04": "2024-01-03T20:00:00", ...}).Beta Was this translation helpful? Give feedback.
All reactions