Given that the routes in your enabled %CSP.REST class point to class methods you should be able to debug/step thru line by line by calling the class method. In the case where you might have a POST/PUT for your route that calls the class method you can always define the formal specificaiton of the class method to accept parameters and then have the code in your class method look at either your parameter values or %request.Data to determine if the class method is being called by a Http call or your simple debugging.
When building data for a cube, either a full build or a synchronization, think about it this way. The code generated to support this essentially does a SELECT AllOfYourDimensionsMeasuresRelationships FROM SourceTable.
when you have non primary field references these expressions are evauluated as ObjectScript expressions.
These are documented but not on a single page
%sourceID although this is typically thought of being used in a detail listing specifically if you chose the option for whereas the other's are when defining the cube dimension, measures etc
You may have an issue with the format of the date.
What is the datatype of
Are they %Date, %TimeStamp, %UTC, or PosixTime
I'm not certain but does MAX(somedate) cause the value to no longer be in a format that would support
WHERE dateField >= anotherDateField
When in Analyzer you can see the actual query being run aftet the query runs by clicking on the Show Query button in the toolbar
which it seems like you have done so as you have
WHERE source.%ID IN (SELECT _DSsourceId FROM MyTable.Listing WHERE _DSqueryKey = 'en3460403753')
you can copy the query SQL Query Listing and paste into (albeit remove the portion that has
WHERE source.%ID IN (SELECT _DSsourceId FROM MyTable.Listing WHERE _DSqueryKey = 'en3460403753')
)
System Explorer->SQL and take special note of the Runtime mode of the query.
The Runtime mode has the greatest impact on columns that are
%Date
%UTC
as these columns will have different values based on the runtime mode(Logical/Display/ODBC)