Forum Discussion
Connect Sage Intacct to Power BI
Hi community !
I would like to use Sage Intacct general ledger as source to Power BI.
Has anyone ever faced this problem?
Has anyone ever used one of them ?
I ve found all this connectors :
- Synchub
- Cdata
- Alumio
- Tray
Has anyone ever used one of them ?
Thank you so much for your answer !
Hi Anonymous ,
Here is blogs talking about how to use the CData Connect Server to generate an OData feed for Sage Intacct, import Sage Intacct data into Power BI and then create reports on Sage Intacct data in the Power BI service.
Import Sage Intacct Data into the Power BI Service for Visualizations
Author Power BI Reports on Real-Time Sage Intacct Data
Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
4 Replies
Hi Anonymous ,
Here is blogs talking about how to use the CData Connect Server to generate an OData feed for Sage Intacct, import Sage Intacct data into Power BI and then create reports on Sage Intacct data in the Power BI service.
Import Sage Intacct Data into the Power BI Service for Visualizations
Author Power BI Reports on Real-Time Sage Intacct Data
Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.Hello Anonymous , how is the CData connector working for you, please? Have you tried it? Or did you choose a different approach to get data from Intacct to PBI?
Hi all, I'm jumping in a bit late, but thought it might help to share what we see trip up most Intacct and Power BI projects:
API throttling: Raw connectivity misses the point. It’s the throttling that’s the pain. We’ve seen GLDetail pulls crawl at 200 rows/s. Power BI’s "incremental" refresh isn’t a true delta. It must reload entire multi-month partitions when rows change. So your refreshes drag, and big datasets hit daily API limits.
No star schema: Raw Intacct objects (APBILL, GLDETAIL, etc.) perform terribly in Power BI. Microsoft says a star schema is essentially required for anything serious, and that’s understating it. Building production-ready transforms is a nightmare, and denormalisation errors create duplicates that aren’t acceptable in finance data.
The fix for both points is to put a data warehouse in between. Hit Intacct hard once, then delta thereafter. Transform to a star schema in a PK-enforced database, and let Power BI refresh from that instead.Full disclosure: I’m the CEO of Zap, and we built our product for this Intacct → warehouse → Power BI (through XMLA). I’m not aware of any other product built specifically to this end and with Intacct in mind. You can check out how it works here: https://www.zapbi.com/platform-pages/power-bi-integration-sage-intacct
Cheers
