Loading Profile...
Multiple Date Attributes are not Working (in the new release?)
(Prior to the recent release this worked ok.) I uploaded some data with multiple date fields, most containing at least some NULL values. During the initial upload I selected one of the date fields as a Date field. Let's call that "Date 1". After the upload was done I used the new mapping functionality to map each of the other date fields to the Date dimension to create additional Date attributes. The sample data looked good and I got no error messages.
However it appears none of the other Date attributes (other than Date 1) has a value (or they all are mapped to NULL). When I use one as a "How" field the data is not split accordingly. When I use one as a filter I get a "all data has been filtered out" error.
However it appears none of the other Date attributes (other than Date 1) has a value (or they all are mapped to NULL). When I use one as a "How" field the data is not split accordingly. When I use one as a filter I get a "all data has been filtered out" error.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Tom, I think that I know what is the problem. We have added the NULL date value to the time dimension to support the empty date fields in the uploaded files. We have experienced a specific problem with the mapping that resembles the behavior that you are describing. The problem is with the automatic conversion of the date values. All values that can't be converted to date (even values like last name) are converted to NULL and match the newly added NULL value in the date dimension. I assume that for some reason (bad date format) your values are converted to NULL instead of a date value. I assume that you are using the ISO (YYYY-MM-DD) date format. Can you please double-check that the values are formatted properly and that you are mapping them to the correct format (US vs. ISO)? If all of the above is OK, would it be possible to try to use the US format (MM/DD/YYYY)? Please note that you need to always us the 2 digits for day and month (01 instead just 1) and four digits for the year.
I'm sorry for the inconvenience
ZD
I’m frustrated
1 person says
this solves the problem
-
Inappropriate?I am trying to use ISO dates and now the "Join With Other Dataset" section on the right side of the page is empty (it doesn't contain any links to join to other datasets like Date or Geography) when I select one of the date attributes to map it to the Date dimension.1 Comment Add a comment
This solves the problem
-
Please double-check that you have all dates in the YYYY-MM-DD format and that the month and day have the leading zeroes. Even one incorrect value can prevent the mapping. -
Inappropriate?Similarly, I have a zipcode field and the option to join it with geographic data is not presented.
-
Inappropriate?I§m not surprised with the ZIPcodes as we use the Census 2000 ZIP database that is a bit outdated. I bet that you have some newer ZIPs that are not in our dimension. We plan on refreshing the Geo data.
I’m frustrated
-
Inappropriate?I downloaded Good Data's zipcodes and used them to clean my zip code field. This process left NULLs where whatever had been in the zipcode field didn't match one of Good Data's zipcodes. I uploaded the data from scratch and still didn't get the option to map my zipcode field to your zipcode dimension.
-
Inappropriate?I am still having trouble getting multiple date fields "mappable" to the Good Data date dimensions. I have tried YYYY-MM-DD and MM/DD/YYYY formats and in both cases during the initial upload it lets me map a date field to Date, but after that it doesn't give me the option to map any of the other date fields to Date.
-
Inappropriate?An update: I got multiple date fields to map to Time dimensions. I had to do it from the DataSet page instead of from the Attribute page.
EMPLOYEE
