It seems the sql queries automatically defined in Experiment Assignment Queries for data sources is incorrect. When changing to the correct queries it will not let me save the changes since there is no data yet in my data warehouse for those new columns. I am hoping that when the data is finally tracked and exported I can paste those queries back into the sql for the Experiment Assignment Queries for my data source and it will work correct. @brief-honey-45610 Does this sound correct or since there are more people experiencing this is there another separate issue with saving custom sql on Experiment Assignment Queries datasources?

I summarized the issue for our Engineering team and I'm waiting to hear back from someone. I'll keep you posted. Thank you for raising this (again)

Quick update, I am actually able to save my queries without them working yet. There was a checkbox for test query before saving that was not allowing me to save the custom queries since they had no row or unrecognized name. I am thinking that my issue is solved since those new tracking attributes are waiting to be released have yet to be tracked or exported to the data warehouse

Hi again, @careful-grass-28115 and @clever-napkin-58859 and @quiet-spring-52073. This issue arose because we render default dataset names in the default Experiment Assignment Query if we don’t have enough information about the dataset. The resolution we will be implementing in our next release (2.6) is to run a validation to make sure the properties have already been set by the user, so that the Experiment Assignment Query can use those instead of a default value. In the meantime, you’ll need to edit the Experiment Assignment Query if this error occurs again. If it doesn't save after you've edited it, try the steps Tyler outlined above, and also make sure there are no errors in the query.