On the development server I have an account configured to use the EST/EDT timezone for the API calls.
It seems that with this configuration, the API calls return a date with an incorrect time.
For example, I have created an envelope at 12:46 GMT but the API to get the envelope summary is returning the following date:
2015-06-10T15:46:25.8165848Z
If I am not wrong, the time is incorrect because Z is the timezone for UTC and so I was expecting 12:46:25.8165848Z.
Setting the timezone for the API calls to pacific time, the date returned is correct:
2015-06-10T12:46:25.8165848Z
Am I using the API correctly?
For example the API call:
GET https://demo.docusign.net/restapi/v2/accounts/917973/envelopes/b7c31971-53e1-417e-b132-e27514befdcf/audit_events HTTP/1.1
returns an incorrect time for the audit events when the user is configured with a timezone that is not "pacific time".
DocuSign support confirmed what #luis-scott wrote. For now it is not known when the bug will be fixed.
Related
we are using CSOM to communicate with SharePoint Online.
Since April 16th, 2021 we recognize http 400 responses from different parts of our code using CSOM calls from time to time. We added status 400 to our internal retry logic. Executing the same call a few seconds later succeeds. So pretty much a wrong status code.
It seems like SharePoint should generate a 429 throttling response at that time and somehow generates an incorrect 400.
Does anybody else experience the same?
Regards
Sven
Microsoft has fixed the issue on May 7th as reported here: https://github.com/SharePoint/sp-dev-docs/issues/6955
We could not find any http 400 failures in our logs after 5/7, so the fix seems to work in our case.
When processing webhook posts, I see the dates are all in my (Eastern US) timezone. This is reported correctly if I apply the option to include Time Zone Information.
I can work with this, but I have a few questions:
why not send in UTC, which is used consistently -- I believe -- throughout the API? (At least, the REST API)
Is Time Zone Information working correctly? I ask because this report says it doesn't support fractional info, such as India's UTC+5.5 correctly.)
What Time Zone is used in the webhook posts? I have changed both my personal preference and my account setting to Katmandu, but I still Eastern. (Thus, I cannot test #2 myself.)
Thank you
1.) Most datetimes coming back from API are UTC, however SOAP and Connect messages follow a hidden account setting. You will need to ask support to change it. It's called "Time Zone used for Connect and SOAP".
2.) Fractional datetimes should work fine
3.) Webhook and SOAP currently use the same time zone as mentioned above. Your UI preferences (account settings and personal preferences) that you see are aimed at UI users. Since you are an API integrator, they follow a different setting.
When I receive a user request I would like to respond with a date with the user timezone. Actually, I can only respond with server TZ
Unfortunately, DialogFlow doesn’t make it easy by simply telling g you what timezone the user is coming from. The best you can do is ask the user for their timezone and then save that to do date/time adjustments in future responses.
This can be optimized a bit for users accessing your agent through Google Assistant by using the new permissions API. See https://chatbotsmagazine.com/personalize-google-assistant-skill-with-user-data-328f5e0860a0
If your user responds to your agent with the parameter of #sys.date-time type, you will receive in your fulfillment the value in ISO-8601 format like "2019-12-17T22:00:00+02:00". The last 6 characters represent a timezone offset. You can use it and calculate the target local time of your users.
Currently i am using Bot Framework with Node for my chat bot and i am using API AI as my Natural Language Processing.
My question is, let say the user replied with "yesterday" or "today" or "tomorrow" and it is base on the server time. Now, it will go wrong if a person in Australia says today at 6 AM in the morning and their time which is in GMT will still be previous day and this gives a wrong date.
May i have suggestion on how do i solve this timezone issue?
Each API.AI agent has a default time zone setting which can be altered in your agents settings (documentation here) which will be used to determine the meaning of user's date/time queries like "tomorrow" and "yesterday" and "3pm":
If you're using API.AI's /query API you can send the timezone parameter in the request JSON to indicate what timezone the user you are sending the request on behalf of is in.
I have recently noticed that retrieving the LastDateTimeModified (through the WebService API) from Acumatica gives me the date and time in a very different time zone - I am guessing GMT time.
However when I view this through a Generic Inquiry it seems that it is showing the correct time - based on my Time Zone set up in the user profile.
Is there a way to get the LastDateTimeModified in the correct time zone when retrieving from the Web Service API. I have attempted changing the Time Zone for the SDK user with no success
Thanks,
G
For most screens, except a few CRM screens, the LastDateTimeModified and CreatedDateTime are stored in the same time zone as the database server machine. When reading it using web services, you are retrieving the raw value form the database, with no timezone conversion. It is up to you to convert it to the desired timezone.
The Help->Audit History panel does a manual conversion to the current user time zone. I have not been able to get the generic inquiry to show the time as you mention in your question; it is only showing the date.