Where did that join condition come from?

Being a consultant, I see many different MSTR implementations and the following issue pops up ever so often.

A report that always works, suddenly... doesn't.

After checking the change log (no changes were made to the report) and making sure there is data in the warehouse, I find an interesting addition to the report SQL.
Where it was always:

SELECT a1.day
FROM
Fact a1
join LU_Date a2
on a1.day = a2.day

now it is...

SELECT a1.day
FROM
Fact a1
join LU_Date a2
on a1.day = a2.day 
and a1.deliverydate = a2.day

Where did the additional join condition come from?

Trigger MicroStrategy Events from ETL

Use Case:

You have multiple MicroStrategy iCubes that you want to be able to refresh from your ETL process, which would allow you to refresh them only when certain criteria have been met (like after data load has been successfully completed)

Using the Command Manager tool you could refresh each cube separately, but it might be easier to have all cubes refresh when a specific Event is triggered.

Collation Conflict Error

We got the following error at one of our clients:

Report: Status: Execution failed Error: SQL Generation CompleteQueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [42000:468: on SQLHANDLE] ..... Cannot resolve the collation conflict between "SQL_Latin_General_CP1_CI_AS" and "Latin1_General_CI_AS"

This error occurred on one of our reports after we switched our DW database to a different server.
We are running on MSSQL 2008 R2.

Advanced Custom Grouping based on Prompt

How do you display prompted elements on a report, and at the same time display all those not selected as a single Element called "Other"