Recently we migrated 2013 sites to office 365 using metalogix tool, in one of the site Task list is migrated with all content but the date which is displaying in due date column is one day ahead of the date in source site
Ex: due date is 02/03/2017 in source but in target it is 03/03/2017
are there any teams which faced similar kind of issue??
what might be the fix for this issue??
You have migrated your SP 2013 sites to O365. Your SP 2013 uses your local timezone and O365 uses its timezone. When you migrate SP2013 to O365, it changes the DateTime value(in your local timezone) to O365 timezone. Thats the reason for 1 day ahead.
We're experiencing a similar issue now migrating from a SP 2007 on prem to a SP 2013 on prem. In one list, the dates are "1/01/1900" but the migration fails with Metalogix reporting that "1899-12-31T15:00:00.0000000Z" is an invalid date for those exact fields.
Not sure why at the moment as both servers appear to be set in the same time zone with the same locale.
UPDATE: This is happening on our servers because the SP2007 is set to GMT time whereas the SP2013 is set to UTC time. A default time value in a date/time field entered when the user cannot enter a time component is 12am. So during the migration daylight savings is/isn't taken into account on one of the servers. We've pushed those particular records one day ahead -> when they get migrated they fall back to 01/01/1900 11:00pm -> all we care about is the date so they come across.
Related
I'm building few dashboards in Apache superset. All my available timestamp fields are in UTC timezone. (for example fields are, class_start_time & class_end_time).
I want that in the timezone the dashboard is opened all the timestamp fields will be automatically converted.
For example, I'm opening dashboard in Norway , so the UTC data should be converted to CET timezone of Norway.
I have tried to add some value here in Hours offset but its not working.
Can you please guide how we can achieve this.?
Just for reference :
In Kibana dashboards (ELK stack) have feature to automatically convert the timezone into which it is being opened. So I need same thing in Superset.
Normally you would be able to set this with environment variables when you start the program or container. In Apache Superset, this is not possible. There is an ongoing discussion on Github about this issue. One GitHub user posts the problem and workaround, which is far from workable:
Daylight savings causes issues where users have to update datasource
timezone offset for each datasource twice per year.
So the only thing you can do is update the hours offset twice a year. To make matters even worse, if you use Postgresql, this may not even be possible due to a bug as described here.
When I Insert timestamp into Postgres table in EST (2019-02-21 05:37:46) and in Postgresql table is stores in IST (2019-02-21 16:07:46). I want time to be stored only in EST. Can anyone help me to fix this issue?
In postgres, you can change the default format mask for datetimes using the set n postgres, you can change the default format mask for datetimes using the set datestyle
for more details follow this link
also refer this link
To my knowledge, there is no setting in PostgreSQL that would trim seconds from timestamp literals by default
In general you should handle all datetimes in UTC, because these are absolute timestamps that are always correct. Even if you are only going to have users in the EST time zone use your website, the EST time zone has daylight saving time (DST) in the summer, so you could get buggy behaviour when the time jumps (especially since there is an overlap of one hour when the clock goes back). This means:
Your code should use UTC timestamps to make calculations and pass around
Your database should store UTC datetime (which PostgreSQL does anyway).
You should only transform to a local time zone when presenting the data to the user. This is default behaviour in Django:
USE_TZ = True by default
TIME_ZONE = "America/New_York" to set default time zone, which will take into account DST
So when you're saving a time-aware datetime to the database (in EST say), the database stores it as UTC. When you fetch and display it, Django will show it in the current time zone of the user (EST in your case). When you query the database directly using a tool, PostgreSQL gives back the UTC, correct datetime, but your shell or tool might display it in the local time zone. You can format your query to use a different time zone using the links posted by #c.grey in the other answer.
Read up on the details here
I have a fairly simple tabular sales model (Customers, Products, Sales) deployed to a SSAS 2016 server in tabular mode and I have a few measures setup on the sales table, things like total value, total kgs, total units, but after deploying the model, they do not show up when connecting with Power BI. Is there a setting that i might be missing somewhere that could be stopping the measure from showing up?
Update
One of the things I have tried, is to run the Create Script Task in SSMS to see if the measures get added as part of the SSAS Database create script and it appears that they are not there from that angle either.
I have figured it out... I haven't deployed it just. It was the separator between the naming of the measure and the formula that was the issue. I just had the equal sign (=) instead of the colon equal (:=) which is what DAX is expecting. It wasn't until I tried removing the name and leaving the formula much like an Excel formula that the formula editor decided I had screwed up and fixed up my naming of the measure. It was at this point that I found the issue with my naming without the colon.
The measures are now calculating as expected in VS and they now show up on the Tabular Model Explorer.
The odd thing though is that there were no errors at all to say that there was an issue. The deploy just worked without any issues. So that is one to watch when your measures don't show up.
Update
I have deployed to my on-premise 2016 server and the measures now show up.
I just followed instructions on django website https://docs.djangoproject.com/en/dev/ref/class-based-views/generic-date-based/
DayArchiveView was working and TodayArchiveView was showing the date for the next day. I have a 3 hour difference on my time so it's hard to debug it when I can only see the difference at 9 pm at night.
I have USE_TZ = True, and installed pytz. Can I just do {% load tz %} {{ value|localtime }}
From your comments, it seems changing your settings.TIME_ZONE solved the problem. You further wanted to know how to ensure that visitors to your website get the Archives for their current day. This is explained in Django docs as the difference between default timezone and current timezone and in the next section, as wel.
In short, TodayArchiveView will show entries belonging to the same date for all users. This date is the current date based on your settings.TIME_ZONE. This is what you would expect to see in most websites. For e.g. you have an article for Feb 17 in your timezone but a visitor comes from a timezone where it is already Feb 18. They will not be able to see the article in TodayArchiveView even though it was published less than 24 hours ago! Most forums or blogs work in their server time and date.
As the docs explain, there could be conversion to the end user's timezone in views and templates, but it would be confusing if it is done at the model layer.
When I execute getDefault() on a java.util.TimeZone object created from ColdFusion 9 I am getting "Pakistan Time". We are in the eastern timezone and our server (Windows 2003) is reporting proper timezone. Where would ColdFusions JVM be getting this timezone?
TimeZone: Pakistan Time (Asia/Karachi)
try this: http://troymurray.blogspot.com/2007/12/coldfusion-timezone-change.html(deleted)
Content retrieved from Google's cache:
ColdFusion Timezone Change
So I've been working on a component to accept data from whatever and insert it into our Oracle database, no big deal. But, I need to do this with date and times, which gets really sticky with Oracle. I noticed however that my ColdFusion function Now() was returning the wrong time, about 5 hours off, which corresponds to my timezone (-5).
I looked all through the ColdFusion Admin but wasn't able to find anywhere to specify this. I then seem to remember that when I setup this server, and installed ColdFusion on it, that I had the wrong timezone set and somehow that must have been saved. Since ColdFusion relies on Java I needed to change the time zone with the Java Virtual Machine (JVM) that ColdFusion runs. Here is how I did it:
First, find the correct timezone ID for your location. I found mine by going here.
Login to the ColdFusion Admin
Under Server Settings go to Java and JVM
Locate the JVM Arguments textarea
Add a space after the last character, then "-Duser.timezone=" and then your timezone ID.
Click the "Submit Changes" button
Restart the "ColdFusion 8 Application Server" service
Verify your time shows correctly now.