Any metric or chart that checks if a date field is...
# gooddata-cloud
r
Any metric or chart that checks if a date field is null or not no longer works and the chart will not display. The checks looked like "Deleted Date != NULL". Anything with this kind of check has failed and I can only make it work again if I remove the where clause with the null date check. Having to remove this check breaks our metrics by including invalid data. Is this an issue you folks are aware of?
i
Hi Rob, I believe that this is related to our previous thread, correct? Please let me quickly check if there were any recent changes tied to the MAQL or specifically tied to the Date Attributes.
Hi Rob, Could you share with me some example of affected insight, please?
r
Yes, this is related but I now know what caused the failures. We have tables that use date fields like "completed_date" and "deleted_date". We filter by these fields by checking "is them completed" which looks like "completed_date != NULL" or "is the item active" which looks like "deleted_date = NULL". Where ever we had one of these date null checks, the chart fails and will not display. Here is are some examples of MAQL that caused failures:
Copy code
SELECT IFNULL((AVG( {fact/duration_seconds} ) / 3600),0) + SUM({fact/zero.zero}) 
WHERE {label/completed_date} != NULL AND {label/deleted_date} = NULL
Copy code
SELECT IFNULL(SUM({fact/totalseconds} / 60),0) + SUM({fact/zero.zero})
WHERE {label/facility_deleted_date} = NULL
I am working around this issue by creating views that do the filtering instead of relying on the MAQL to do it and then replacing the tables in the data model with these pre-filtered views.
Since GD reports that a visualization does not exist when there are problems like this directly in the visualization configuration instead of a MAQL metric, I had to recreate about half of all of our visualizations in order to get them to work again. Many of those aren't even doing null checks so I still do not know why they failed. This "visualization does not exist" issue is a big bug in your system. Does GD have any plans to fix that issue? It is a big headache for us whenever a developer accidentally makes a change that breaks a visualization and we are forced to recreate the whole thing instead of being able to just go in and make an adjustment.
@Ivana Gasparekova Is this enough information for you to look into this problem?
i
Hi @Rob Wilburn, Thanks a lot for all the details and once again, I am sorry for the situation. Could you be so kind and share with me the direct URL to affected workspace, so we can try to replicate the issue and fill in the possible BUG report? Feel free to use the DM for that, please.
r
I have rebuilt all of our production visualizations to get around this problem so there is nothing to see there. I am restoring an old version of the workspace to a test workspace along with prod data. Hopefully that will give you what you need. I will get you a link as soon as it is ready
i
I see, I actually hoped that we can prevent the manual rebuilding, but I understand your actions since you probably needed working analytics for your work. Thank you, that would be great.
r
@Ivana Gasparekova I sent you a DM with a link to a workspace that has the original visualizations where you can still see the problem