With XLPublish you can use our ULookup feature to establish relationships within the Target file. These would ensure that there will be no Orphan records in the Child Table(s) and would assure relationships in the Data Model, should you import the Data Model into PowerBI.
In order to prevent invalid data, XLPublish automatically analyzes all fields in Target files and flags those in which there are inconsistent data types (i.e. dates in a date field that are not in correct date format and thus invalid or use in PowerBI). You can then make corrections in your Source file and then Republish when the data is all consistent.
Users with a developer license may add DAX Measures in the Data Model within Target files which can be subsequently imported in PowerBI. These DAX formulas then become fully compliant “Measures” in your PowerBI Datasets exactly as you might create them using Power BI Desktop.
“Developer” users may use PowerQuery in Excel 2013 or Get and Transform in Excel 2016 or later to transform the data in your Target files. An example would be merging multiple tables (from different Source Files) into one Consolidated Table in the Data Model. This would then be imported into PBI.com.
If you import into PowerBI.COM directly from your Target file, Data Model tables get imported automatically (including relationships, measures, etc.). Then if that data is used as the data source for a Power BI Desktop PBIX file these same attributes of the Data Model flow to the PBIX file as well. If you make changes to your Data Model in the Target file, these changes flow to PBI.COM and to the PBIX file automatically. Note that, if you connect to the Data Model directly in Power BI Desktop, changes, including new or renamed fields or Tables, will NOT propagate through from Excel.