DI/DS Improvements & Suggestions

[dlaplant]

Flat files: a template flat file like a template table or xml

Flat files: ability to automatically ignore columns to the right of those defined in the flat file format

[wdaehn]

Just asking how close these features get:

https://wiki.sdn.sap.com:443/wiki/display/BOBJ/How+to+create+a+flat+file+format+from+a+Query

https://wiki.sdn.sap.com:443/wiki/display/BOBJ/Errorhandling+in+file+formats (Scenario 3)

[dlaplant]

That works. Thanks.

[dnewton]

Idea: Some of the Table Compare options should be set-able through global variables, to allow dataflows that handle both Incremental loading as well as full re-loads.

In particular, if you could set the "Detect Deleted Rows" and "Comparison Method" options to also read a variable, you could have a single dataflow that does incremental (no deletion detection; comparison method is row-by-row), and a full re-load (deletion detection; cached comparison table).

Without this, you need two separate dataflows.

[dnewton]

Create and include in the DI installation, a BO universe to report on the DI repository. This would seem like a slam-dunk integration point between these two BO products...

http://www.forumtopics.com/busobj/viewtopic.php?t=116709

[dnewton]

The Merge transform should have a radio button for "Merge All" versus "Merge Distinct". Similar to the MERGE ALL vs MERGE in SQL itself.

Yes, you can add a Query transform after the Merge with the Distinct checkbox checked, but a radio button choice would make for a simpler dataflow design (fewer steps) and would make it clearer to the new DI user what was going on.

[bhupendra_fatnani]

My wishlist :

1) To be able to go back to the designer of lookup_ext() function once it has been implemented. It is a pain to manually decode the whole function because once cannot go into the designer mode again.

2) To have more compatibility in the lookup_ext() function like the usage of 'AND'/'OR'/both clauses in the conditions box. As far as I know, all the conditions in the box are joined with 'AND' which limits the usability of the function.

3) To have a small box at the end/beginning of the Administrator page which asks for the "page _ of _ " to go rather than clicking the next page button those many times.

4) To have the compatibility of (+) instead of/and having an outer join box in the Query transform. If there are 5 tables to be joined and if the query requires outer join only on 2 tables, even then one is forced to apply the outer join involving all the tables/queries.

[bhupendra_fatnani]

5) Include more functions in the inbuilt functions library. BO XI R2 Webi has wonderful functions and DI seems to fall short of useful functions like them.

[wdaehn]

1) I never use the lookup_ext in a mapping but as a new-function-call for exactly that reason.

https://wiki.sdn.sap.com:443/wiki/display/BOBJ/lookup_ext


2) Use two lookups for the OR. So if the condition should be col1=1 or col1=2 you can have two lookups with each condition and in the next step you decide which of the two you actually take via a ifthenelse(). I know, not perfect but with ORs you would need to support brackets as well and then the GUI gets really complex.

3) Wait one or two months and then DS 12.2 supports that!

4) True.

5) True. Can you list the most important ones for us?

[dnewton]

A new transform, something different than History Preserve, more like "Existing Column Preserve", that does the following:

- If the data in the target table has a value, leave it alone
- If the data in the target table is null, then fill in the incoming value

In this transform, you could click on each column and the tab/dialog area below would have options for:

- Normal (pass-through)
- Preserve if not not null
- User-specified condition (and you could put in your own WHERE-like criteria)


This is useful for some columns where you always want to preserve a value like "initial load date", even if the row is later Updated (rather than inserted). But you want to have the same dataflow, and not have to resort to bringing in the target table as a source.

In fact, now that I think of it, this could be added into the Table Compare transform. Since you already have to read the entire target table's row for that transform to work, you could have another tab in the table compare that lets you specify this column-by-column behavior.

[nitrobrother]

How about the ability to have multiple instances of the Designer open at the same time, with each one pointing to a different repository?

For example, I'm in the development environment and want to go look at something in the production repository. Currently I have to exit Designer and restart it, point it to the prod system, look at what I need to (assuming that CRS hasn't kicked in and I can remember what I was after), then lather-rinse-repeat to go back to my development environment.

[umak]

How about "View Where Used" ability for variables!!! right now is there a way to find it?

[dnewton]

[dnewton]

I had a requirement to compute an aggregated fact table, and only show the Top customers or Top products in the result. This was a minor pain to do, as it required several Query steps in succession:

- Aggregate the measures
- Sort by the customer/product and then by the Revenue, in DESC order
- Add a "gen_row_num_by_group" column
- Then filter out just the top 10.


If there was a "Top" transform, it could do all of the steps above. Just specify which columns are the dimensions, which are the measures, and whether you want the highest or lowest values, and how big the TOP should be. It could do all of these in one step.

[umak]