I wants to see the data model in my report can I see the data model like the QlikView there is the option available tableviewer. I am searching for this type of feature in Tableau.
Thanks and Regards
Surbhi Sahu
Business Intelligence Solution Provider
www.bispsolutions.com
No you cannot see the data model in tableau like the way you see it in qlikview .
Data modelling maybe completely handled by some other tool of choice in tableau.
Related
I am trying to change a selection table within our packing list menu in our SAP system, but I do not know how to do this. My colleague, who is out indefinitely, has created a table of packing materials for our warehouse staff. This table is now to be extended by two further entries. The selection table is in the packing list table DLN7. I have also shown this in the picture attached.
So far I have checked all custom tables and custom windows. However, the table displayed is not there. Does anyone know where in SAP I have to look?
I would be very happy to receive further hints on this.
Thank you very much in advance.
I'm completely new to Qlik Sense and also with the coding syntax used in the data load editor.
I select the Account object from Salesforce through the connector and I select the fields Account ID, Country and LastActivityDate. Then I was surprised I could not filter that object by, for example, Country = Netherlands.
Now, I tried to do something in the sense of: WHERE Country__c="Netherlands", but of course it's not as easy as that.
I need to implement these filters:
Country__c = Netherlands
LastActivityDate is from 1st of May and beyond
Hate to be vague but these links should be of help.
Filtering data from data connectors :
But Qlik disclaims that the ability to filter is not available for all connectors.
https://help.qlik.com/en-US/sense/September2018/Subsystems/Hub/Content/Sense_Hub/LoadData/Filter-data.htm
If all else fails, load everything and make use of this little tool. Be weary of getting dependent on it.
http://tools.qlikblog.at/SetAnalysisWizard/QlikView-SetAnalysis_Wizard_and_Generator.aspx?sa=
I have a data model using a private data source (not from a Subject Area), so I need to do this with a BI Publisher Report (not an Analysis).
In the data model I have a column called 'Financial Plan Type' that contains a few different values such as "Forecast", "Adjusted Budget", "Original Budget", etc.
I want to create a pivot table that pivots this column and then creates a variance column between "Adjusted Budget" and "Forecast" as example. Obviously I have an 'Amount' field in the table too.
It doesn't seem that I can do this directly in the report as the formulas and flexibility seem to be limited for the Reports (although I'm not 100% sure of this as I am fairly new to OBIEE), but I was thinking that I could adjust the data model to union in a variance amount or do something else with the data model to make this work. Does anyone have any ideas and/or best practices around doing this either in the data model or in the Report itself?
This going to be abstract, but you can do this in BIP or Analysis, depends on what the data source looks like.
If you have are able to compute the variance as an extra element in the datasource (might need to model it), then BIP RTF template designer does support Pivot tables. You might still need to add some XDO code in the loops.
If you are inclined to OBIEE, you can create your OWN data source on OBIEE. You will have to use the RPD data modeller if you are on OBIEE on premise, or write the transactional SQL if you are OTBI on the cloud.
Either way, the trick is to have the variance already computed in the XML, so BIP/OBIEE can simply print it off.
I'm using Entity Framework 4.3 and I'd like to create a view because of the low performance of some selects. Is possible to do it from code?
Peter Kellner has mentioned in his article:
With CodeFirst, making views is problematic because you are not actually creating your own tables and columns so going directly into the database is really not something you should do. Creating a view basically violates one of the main purposes of CodeFirst which is to remove you from having to see database details. Making a view now tightly binds your model to that view and if you change you model and not the view you are in for trouble.
For more information visit Entity Framework Code First From Microsoft, Best and Worst Practices and How do I define a database view using Entity Framework 4 Code-First?
I want to modify the view of 'Activity' entity, opened the view and try searching for edit filter criteria option and it's not available on view form.
please see below
Can you please help to advice me on how I can add filter criteria for this view above. Or how to make it visible the option 'Edit filter criteria' on the form of a view.
Any suggestion will be much appreciated. Welcome for any feedback...
I don't know any way to do that, but you can do your custom views and for example change the default view for that entity. With custom view you can change everything.
See here step by step: http://www.powerobjects.com/blog/2008/08/11/creating-and-editing-views/
What you want is impossible to achieve. Pedro's suggestion is your only option. Create your own Activity view, and then you can create your own filters. You definitely cannot create your own Associated Views. Public Views are the only ones you will have a hope of creating or modifying, and in this particular case, you are still restricted.
There are various places spread throughout CRM where you will run into problems like this, where an entity, view, or field is "locked down". This is the cost of starting with platforms like CRM which are a blackbox that only offer customization up to a certain point.
The problem in this specific case has to do with the nature of activities and the various activity types. Under the hood, there really is not a traditional record type for Activities. The Activity entity is really a "pointer entity" (note the internal name "activitypointer"). Activities really point to other entity types (in this case Activity Types) such as Email activities. The Email entity is more of a traditional entity which you can run standard queries against--but even still that is "locked down".
This additional layer of complexity makes dealing with Activities programmatically more difficult (ex. querying the data, modifying the data via a plugin/SQL, etc.) and, in this particular case, makes even the most basic customizations impossible.