Build React Native App (4) - Redux, Jest, and NativeBase

Image
From this blog, typescript feature will be added. There are couple of ways to implement static type checking like; flow from facebook, PropTypes and Typescript. Typescript is well integrated with Visual Studio Code and supports better linter, error messages, and intellisense. Reference site Github Sample Ex4 Currnet version D:\GitRepo\reactnative>npm --version 6.3.0 D:\GitRepo\reactnative>react-native --version react-native-cli: 2.0.1 react-native: n/a - not inside a React Native project directory D:\GitRepo\reactnative>yarn --version 1.9.4 Creating React Native App $ react-native init ex4 If you want to specify the version, add "--version 0.57.3" at the end. Add NativeBase to React Native $ npm install native-base --save ... + native-base@2.8.1 added 71 packages from 42 contributors, removed 50 packages, updated 829 packages and audited 34989 packages in 138.542s found 0 vulnerabilities $ $ yarn yarn install v1.9.4 warning package-lock.json found. You...

Linking One dimension to another foreign table with multiple keys in SSAS

During developing Product dimension, I had one challenge about linking between product and category. The challenge was that our ERP product model has multiple categories. It allows to link 10 categories to one product which causes lots of issue during building snowflake type connection.

Reference

What is problem

AdventureWorks model for the product

AdventureWorks Product Dimesion Design

As you see from the above picture, Product is linked to the subcategory and the subcategory linked to category with only one foreign key. During adding this foreign table to the main dimension table, most time, users will click Key field from foreign key field and move to dimension attribute pane to add it. If you think that you have two categories for one product, you can’t add using this method for the second foreign table because if you look at property windows for an attribute, there is no place which you can modify the link defintion between primary key to forign key.

It seems that the design of dimension and foreign key for the snowflake should be one to one relationship.

Possible Solution

We already completed to build product table, so splitting foreign talbe to multiple tables is really time consuming task due to the create all tables changing ETL process etc (in our case, it was 10 tables)

The approach is to leave current ETL process and implement using View Table. The 10 view tables for the category were created and in DSV window, we created 10 foreign connection to each this tabel. After that, we can create 10 hierachies as you are looking at below.

Suggestion using View

Conclusion

I am not really expert on SSAS limitation, but it looks like that the Dimension design in SSAS has some restriction. I am not sure this restriction comes from SSAS or Data Warehouse priciple. Maybe using View Table, some of headache such as I had can be resolved easily without any modifying ETL process from SSIS package.

However, implementing Margin using Data Warehouse was really fun and super cool. Next challenge is to build Data Mining on the Margin.

Comments

Popular posts from this blog

Build React Native App (4) - Redux, Jest, and NativeBase

Replacing text in PDF file using iTextSharp

Using GIT(Bitbucket), Visual Studio Code