16 responses to “Doing the “Impossible”

  1. Excellent blog. Have you read the new best seller 25 Laws for Doing the Impossible? You may enjoy the book.

  2. dlheureu

    Hi,
    The Receivables Detailed HATB in SRS has a shared connection called dsGP10RM. Can you please provide more info for this connection? Do we simply need to acces the company DB ? Thank you.
    Denis

    • You should find that connection under the pre-built data connections in the SRS report library, but you can use any company connection as well.

      • dlheureu

        Thank you, I was able to make the connection. Now I am getting syntax errors from the semantic queries. I am not too familiar with this type of query, do I need to do a configuration or turn a switch on. The message seems to come from SQL Server. Thank you again. Denis

      • dlheureu

        Please disregard my previous reply. Everything works well now. My users want to export historical detailed statements to Excel. I will be able to build a detailed report based on this one. This will work perfectly. Thank you again!
        Denis

  3. Kayla

    when I download the rdl it comes over as an xml and I doing something incorrectly?

  4. ian

    I don’t suppose there is a multicurrency version of this available?

  5. Sean W. Trewartha

    Wow, I am impressed with the RDL summary report. Kudos for getting something like this done. I have looked everywhere on the internet for SQL code but no one seems to be able to get it done, including me.

    I do have one question: when I run a historical report, say 6 months into the past, I can’t get the aging buckets to show correctly. Although the balances for each customer are correct, the aging buckets are not correct. What could I be doing wrong?

  6. Sean W. Trewartha

    Yes, I even backed dated that process to the end of month I am interested in. The confusing part is that my historical aging under reports works fine, but the SQL reporting method does not work. I have since found out that both your modified report (summary) and the standard detailed report show the buckets the same (which are not correct)

    • I assume this is because the bucket information comes from the customer summary table, which only stores the current bucket information based on the aging. In order to get a true aging by bucket, you would probably have to build the code to calculate the bucket summary based on the selected records at runtime.

      • Sean W. Trewartha

        OK, so when you use the same report, and look back into history, your buckets are not correct either? I just wanted to confirm……..

        Also, I thought the SQL reports were based on the same logic as the reports built into Dynamics GP under the reports area. Those reports get the buckets correct back through time even w/o running the routines for the aging.

  7. Sean W. Trewartha

    ya, back dated 🙂

  8. I’m not sure. I would have to dig into the reports and examine the bucket amounts.

Leave a reply to ian Cancel reply