In Parts 1 and 2 of this series, we looked at parsing multi-schema XML files using the tFileInputXML and tXMLMap components within Talend Open Studio. In Part 1, we concluded that the tFileInputXML component by itself could not successfully parse multi-schema XML files. In Part 2, we concluded that the tXMLMap (along with the tFileInputXML) could indeed parse multi-schema XML files.

In Part 1 of this post, we looked at parsing XML files using the tFileInputXML component and determined that it is suited for single or uniform schema XML files with a single XPath Root.

Parsing XML files within Talend is pretty straight-forward - that's when the files have a single root node and a single repeating schema. When you have multi-schema, nested XML files, you quickly run into trouble using the same approach as you do with single-schema files.

Talend Open Studio (DI / Big Data and other versions as well) allows you to manage your machine's JVM heap size (allocated memory) in a number of places. Not having the right amount of memory can result in a number of errors including the following:

Specified Order grouping in Crystal Reports has been around for a long time. But there are instances where using the out-of-the-box specified order is difficult at best or not possible due to the complexity of business rules that drive grouping. For example, grouping could be based on the result of evaluating say five independent or nested business rules. In these cases, manual specified order grouping is the quick and easy solution.

Adding a logo to Web Intelligence reports/documents is pretty straightforward. But what if you wanted to skip the repetitive step of adding a logo to every new report - or what if you were looking for a way to be able quickly update the logo in all your reports with a few keystrokes? Luckily, there's a way to specify a default logo for Webi documents.

Unlike Web Intelligence which natively supports drill-down functionality thanks to it's powerful microcube and rich & intiutive design options, Crystal Reports requires a bit of set up to get drill downs to work. And when drill downs are set up correctly in they work beautifully in Crystal Reports. Because the Crystal Reports engine does not feed off of microcubes like Web Intelligence, care must be taken to ensure that aggregates (sums, counts, distinct counts etc...) are computed correctly at different drill levels in the report. The safest and simplest aggregates to use are Pass 1 group aggregates (see multi-pass reporting topic in CR Help). These aggregates are dynamically recomputed at each drill level. However manual aggregates (using formulas) or automatic running totals (all Pass 2 objects) might need to be tweaked to make sure totals are correct regardless of what level of the report is presented.

Today, most organizations actively use some sort of Business Intelligence platform to manage the access and delivery of intelligence to executives, knowledge workers and front-line staff to enable them to perform their jobs. BI platforms have been around for a long time. Some organizations have gone through major conversions from previous legacy systems to adopt modern platforms while others had the luxury of starting from scratch with brand new 'empty' platforms. Whatever the scenario, BI is key to intelligence delivery and productivity.

The propercase function is Crystal's equivalent of the TitleCase function in MS Word. Traditionally used for the titles of everything (books, plays, movies, etc), title case returns a capital/uppercase letter for the start of every significant word – where words like and, of, the and a are not counted as significant.