Dimension Order for EPMA Planning Applications

I ran into a question today where the Account tags for the account dimension (like TB Last and Expense Reporting) were not pushed to Essbase from the EPMA Planning application.  I had this problem a year ago.  The user had the Account dimension first and the Time Period dimension second.  By switching to Time Period first and Account second, the issue was resolved.

When I had the problem a year ago, I opened a SR with support.  My users want Accounts in the Rows and Time Periods in the columns when first opening a new Smart View connection.  The order of the dimensions (Time Period then Account) caused Time Periods to be on the rows, and Accounts to be in the columns.  This was very frustrating for my client who is on his third company using Planning and has always had Account first so the query started with accounts in Rows.