Altova MapForce includes powerful mapping components that correspond to design patterns for data transformation requirements. Analyzing a data mapping challenge up front and following a few straightforward guidelines can uncover data mapping patterns that help simplify creation of the mapping design and lead to an optimal solution. The MapForce Examples project provides sample mapping files and data sets that illustrate many common data mapping patterns. Reviewing these examples and executing them with the MapForce Built-in Execution Engine is another good way to help select the best pattern for your own project.
Tags: Data Quality, Data Quality Center, DQC, EBA, EDGAR, EFM, SEC, XBRL, XBRL.US
Altova is a member of XBRL.US and has recently joined the XBRL US Center for Data Quality to support the Data Quality Committee’s initiative to address the public’s concerns about the quality and usability of XBRL financial data filed with the SEC.
As such, we are pleased to announce that we have just released a new set of EDGAR Tools for RaptorXML+XBRL Server on GitHub. These new Python scripts for RaptorXML+XBRL Server now support validation against the new Edgar Filer Manual (EFM) version 35, as well as implementing all the Approved DQC Guidance and Validation Rules from XBRL.US.
Tags: enterprise mobile, Microsoft, Mobile Apps, mobile development, PowerApps
Microsoft’s recent announcement of their new PowerApps product comes at an interesting time, considering that MobileTogether has been on the market for over a year now. Though Microsoft is a bit late to the game with this offering, their announcement serves to underscore the importance of enterprise mobility and the challenge that MobileTogether was created to solve: businesses need to mobilize essential processes – for all devices – in a reasonable amount of time.
MobileTogether has been filling this need for over a year now, allowing developers and power users with no mobile development experience to build powerful, data-centric apps. If you can build formulas in Excel or write simple SQL queries, you have the technical skills needed to build a robust, sophisticated app using MobileTogether. While PowerApps may be a boon for Office users who need to mobilize simple productivity tasks via basic apps, MobileTogether lets customers take it many steps further, adding rich functionality for processing, analyzing, and collecting data in ways that add value beyond simple mobile access to services.
And in the 2.0 version of MobileTogether, Altova brought the same ease of developing cross-platform business solutions to building fully native apps for all mobile platforms. This is something that PowerApps promises to do – but you only get native apps from PowerApps if you develop the mobile app by hand via the native SDKs on each platform or use a cross-platform framework like Xamarin and then access PowerApps APIs on Azure. In contrast, building cross-platform native AppStore apps in MobileTogether 2.0 is really just a matter of selecting the “Generate code” command from the menu.
The Microsoft PowerApps announcement can be really confusing to parse, so we’ve put together a list of the top 10 reasons why we believe MobileTogether is superior to PowerApps.