Jones01 Contributor

@akeating @MarkSnodgrass Mystery solved. After some trial an error I have worked out that you can only publish changes once in every 5 minute period. This is absolutely fine for us but when you are testing a feature and the interface doesn't indicate this and the docs state the below it can all get rather confusing and…

Thanks for everyone's input. I'll keep you posted when and how I get this resolved.

@akeating thanks. This was 2 pages 6 cards across 3 subscribers. Nothing major. I'm waiting to hear back from domo on this. I'm a software developer and have never released a feature that sometimes works 🤣 Don't get me wrong I love domo but paid features must work.

We are new to domo and domo everywhere so the rate of changes on dashboards at the start is likely to be quite high. Clicking publish and it not publishing is just not an option for us.

@MarkSnodgrass same issues running through the edit option and republish. It even says the correct number of cards in the pages tab but when it publishes the summary number wrong. Unless this updates, my child instances aren't getting the update. I can't be checking all of our subscriber instances every time we make a…

@MarkSnodgrass Thanks for sharing. This appears to be the similar to my experience. So if I add a chart the number of cards published doesn't always go up by 1. It will stay as it is and then if I keep refreshing(republishing) it eventually takes and the subscriber is updated. This can not be correct surely.

@adeshon we have run into the exact same problem. We have the fiscal calendar enabled and while it is great for breaking charts into fiscal periods and for choosing fiscal periods on the date selector the logic on the period over period charts for prior periods doesn't match our clients. Our clients take the date this year…

@MichelleH Thanks, Yes I have just had confirmation that there was an error uploading our custom fiscal year so they are redoing now for me

@RobSomers perfect thank you.

@jaeW_at_Onyx Thanks. Yes that is what I ended up doing but just did it in our source database and brought that over to domo. Hopefully functions like TY_Year get added soon. Thanks

found a solution in the end. As I pull the fiscal year data from our source db each day I have added what the period starts are based on the day it is pulling the data. So my beast modes look like this sum(case when `Report Date` >= `Current Year Start Date` and `Report Date` <= `Current Last Week End Date` then `Value`…

@MichelleH Thank you. Yes I have my own date dimension representing the fiscal year joined to my data. but I still don't get how based on the date today I can calculate the dates for YTD. so at the moment it would get where the Year Column = 2022 but it would need to be able to do this if the date today was the 31st…

@RobSomers Thanks. Unfortunately that won't work as the dataset will be linked to different fiscal years so the solution needs to be flexible. If domo made the equivalent date functions like YEAR etc for the internal fiscal year we have uploaded to each subscriber instance I think it would be a piece of cake.

@MichelleH thanks. Yes I aliased the duplicate column name and that made everything worked. Not sure I agree that it is bound to cause issues as when the data is being imported the situation could be quite easily handled programmatically. I think we'll just stop using select * for now. Thanks again

I can understand it may have a problem but it shouldn't fail silently and then impact the integrity of the data. It should either rename the second key to zone_id_1 or as it currently leaves out the column header it should remove the entire column as well so the data isn't misaligned.

prior to importing into domo. I fixed the issue by aliasing the second zone id. s.zone_id as secondzoneid. Shouldn't really have to do that and select * should just work,

I've just found this has happened again. I was debugging the values in a visualisation as they looked wrong, checking joins etc and found the data doesn't line up with the columns once imported into the dataset. This is crazy. I am selecting from two tables and joining with a column called zone_id. The dataset has the…

@ST_-Superman-_ Thank you. I had been under the impression they were. I have also read about Adrenaline DataFlows. I thought what we had, used what ever Adrenaline is 🤣

it was a brand new connection and query. no union just a join. can't replicate it now unfortunately.

@MichelleH it was just a replace. query was selecting from two tables.

Hi, Sorry I didn't explain myself properly. The data doesn't align to the column names so the data is misaligned by 1 column after a certain point. As in the value and the column doesn't match. I deleted the data and pulled the data again and it worked fine. Very odd.

My dataset has about 5.6 million records and the recursive etl to bring in new records takes 35 seconds. Does that sound reasonable?

@GrantSmith great thanks. Yes I believe I have this all working now. Pulling changes from the source every 30 mins and checking two keys on the records seems to be working.

@SGPA what does the raw data look like as you may be able to do this in a beastmode?

You could create two contacts views. One filtered by buyers and one by sellers then join them both to your main dataset I'm quite new to domo so someone may have a better way.

@GrantSmith thanks for the tip. In the end I just did it in SQL from the connector as I had other columns involved with some outer joins.

@GrantSmith Thanks, that is a great help. My dataset including the dimensions is about 80 million rows as I have added quite a few more date comparisons to the ETL you provided. I may need a simpler version as the ETL to filter the dataset into 2 and join back together has been running for ages.

Hi, Thanks. I think I was misinterpreting this part of the docs I think the normal use case would be to have country as a series as well and the above means you need to name the segment Canada as otherwise you could get the data repeated and a line for each. I was able to get the behaviour I needed by removing the Canada…

@GrantSmith perfect thank you. Not sure how I missed that option. 😀

This is a great idea and much needed for us. Currently we have found choosing a specific date range on the global date selector breaks all period over period charts. This is very confusing for the users. As well as the options listed by @DuncanDomo if a specific range is chosen then the option to choose a compare to range…