Skip to main content
Level 3
January 13, 2022

SQL to JOIN EFStatus to Client Info

  • January 13, 2022
  • 2 replies
  • 31 views

With the latest SDK, some changes in 21 Lacerte tax have affected certain columns and they have been removed from the SDK access. In particular, the C1_G9 and C1_G10 columns contain some EF status info. (see p35 of the SDK Instructions for all removed fields. I'd recommend reading it all over this year as there are some changes highlighted, including new requirements for the connection string, among other things)

There are actually 2 new tables that have been around for a few years - EFilings and EFStatuses that contain all of the EF info, but it's a little harder to parse if you just want the most recent Fed EF Status.

I took it as a challenge to write it into one SQL query, and here you have it:

SELECT ci.C1_0, ci.C1_2, ci.C1_3, ci.C1_4, ci.C1_5, ci.C1_6, b.EFStatus, b.EFStatusDate FROM [DATA1-Client Info] as ci LEFT OUTER JOIN ( SELECT ef.*, efsd.* FROM [EFilings] AS ef LEFT OUTER JOIN ( SELECT efs.* FROM [EFStatuses] AS efs INNER JOIN ( SELECT EFilingId, MAX(EFStatusDate) AS date FROM [EFStatuses] GROUP BY EFilingId ) AS b ON efs.EFilingId = b.EFilingId AND efs.EFStatusDate = b.date ) AS efsd ON (ef.Id = efsd.EFilingId) WHERE (ef.EFID LIKE 'ind.us') ) AS b ON (ci.C1_0 = b.ClientId)

ci.C1_? etc are all of the columns you want to include from the DATA1-Client Info database, so adjust as needed. b.EFStatus is the most recent EF Status for an "ind.us" return for that particular client, and b.EFStatusDate is the date that particular status happened. You could probably remove the WHERE (ef.EFID LIKE 'ind.us') if you wanted to show a line for each filing a client has instead of just the federal.

Hope this helps someone.

    This topic has been closed for replies.

    2 replies

    qbteachmt
    Level 15
    January 13, 2022

    Thanks. Is there anyway to make the link from here:

    https://developer.intuit.com/app/developer/lacerte-sdk/docs/lacerte-get-started

    to this community? There is no Lacerte SDK Community in the Developer Community. Or, this one should go there? It just seems schizo.

    Don't yell at us; we're volunteers
    Level 3
    August 19, 2022

    Just stumbled the SDK and this community after manually doing daily exports for longer than I'd care to admit!

     

    Thanks so much for this labyrinthine query in particular; curious if there are any plans to expose the "eSignature Status" field to the SDK in the future

     

    it is terribly helpful for my clients!

     

    thank you again

    Mike

    Level 3
    January 25, 2023

    Hi Mike,

    I'm new to the Lacerte SDK Group and saw your post.   I have tried to use the SDK for both ODBC and .Net access, but running into some problems.   I have lots of experience using the Quickbooks toolkits, but since there are no examples in the Lacerte SDK, it is a difficult to get started.    I'm interested in either interface, but I have been trying to use the .Net interface with Visual Studio 2019, with little success using the 32-bit SDK.     Any suggestions and/or small example in either VB .Net or C#?   

    Best regards,

    Rick Kamp

    Level 3
    February 1, 2023

    Hi Jason,

    I uinstalled, rebooted and reinstalled the 64 bit ODBC driver from the 1.0.0.347 SDK.

    Your schema code works fine and displays all the tables.

    I still was not able to access the DATA1-Client Info table.   I have no trouble accessing any of the client tables.    Also, I get errors when I access EFilings and EFStatuses.   There must be something incompatible on my server.      For now, I can manually map the client numbers by scanning the files in the IDATA directory.    I have attached the error when I access EFStatuses.

    Thanks for your assistance, but I need to finish my program in the next few days to create the client questionnaires.

    Best regards,

    Rick Kamp


    Jason,

    Here's the error when accessing EFStatuses

    Regards,

    Rick