I have recently developed an odd behaviour in my views. I am trying to generate a simple view that simply lists all entered data of that content type in a table. I have stripped all bells and whistles from the view to get it working but it just won't.
When I create a new view, I can add the relevant fields for the content type, filters etc. It all works as expected. If I then save and try to create another page view for the next content type, all my fields disappear (including the original fields used in the original view). The only fields available are core fields like content:type, content:title, content:post date etc.
I have checked permissions, display values in the content type, searched extensively online. Most people's issue is the relationship hasn't been established but my view doesn't rely on a relationship, it is a simple display view.
Any help or pointers would be truly appreciated.
Thanks in advance Nelle
Drupal 7.22
Views 7.x-3.7
This is a bug in Views. See this bug report for a work-around (disable Views caching and UI Javascript).
Did you tried to remove filters from new page?
There is an important option when you use the same view to create many pages or blocks :
when you edit a field or filter, you should choose where to apply modifications (For All displays or this page (override)
Related
I've asked this question on the Data Studio community page with no response, and haven't been able to find the answer elsewhere.
I need to stop 2 charts on a page from inheriting the page level control that I have set. From searching around, it appears that there used to be an option to disable filter inheritance, which would achieve exactly what I need. However, that option seems to no longer be available.
I've tried manually setting chart level filters that include all of the information I need, but they still seem to be overridden by the page level controls I have set. I've tried creating calculated fields that hard code the information I need, but they are also overridden by the page level controls regardless.
The comparison that I need to make is between an individual store's customer churn, and the average churn for all stores. The report is an overall report for all stores, with the ability to choose an individual store from a dropdown control to narrow down the results, so I can't set it up with chart-level filters as that would defeat the whole purpose.
Does the filter inheritance option no longer exist, or does it not apply to controls? Is there another way around this that I'm missing?
Thanks in advance! :)
Screenshot of the filter inheritance options missing:
No filter inheritance
Example Data Studio report:
Example report
UPDATE: I have figured out a temporary workaround, which is to set up a separate data source that does not include the fields referred to within the controls. However, this is not a workable solution for reports with a number of pages and a number of controls added, as it effectively requires a new data source for every control that I need to exclude (and sometimes that isn't possible).
Group
One way to ensure that the two specific charts (referred to as Excluded_Charts in this answer) are not influenced by Controls (in this case a Drop-down list and a Date range control) is to Group all charts except Excluded_Charts, which would result in the two charts operating independently from the rest:
Right-click on a blank space in the Report
From the drop-down click on Select > All charts and controls on page
Ctrl+Click on both charts in Excluded_Charts to exclude them from selection
Right-click on one of the selected charts
Click on Group from the right-click menu
Additionally, to make sure that the Date range control does not affect Excluded_Charts select both charts in Excluded_Charts and change the default date range from Auto to Custom.
Ungroup
To reintegrate Excluded_Charts back with the rest of the charts in the report:
Select the grouped charts (selecting a single grouped component will highlight all grouped components)
Right-click on one of the selected charts
Select Ungroup from the right-click menu
Additionally, remember to change the default date range of the Excluded_Charts back from Custom to Auto.
Editable Google Data Studio Report (Embedded Google Sheets Data Source)
I seem to have found a solution - the issue is that I was looking at filter inheritance rather than controls. Controls can be limited in scope by grouping them with the charts you want them to apply to.
Thank you very much for your help #Nimantha! I would have never figured this out if you hadn't pointed out that I was referring to filters rather than controls.
In my Winforms application I have a DataGridView control which data source is set to list of objects fetched from web api page. Data is paginated by 200 rows. I would like to create a filter to help user determine which rows are actually to be fetched. The thing is, I don't necessarily want to create custom filter control on my own, as there probably are ready controls (are there?). From open source options I've found brilliant Excel-like Advanced DataGridView by Zuby, which seems to be further developed by Davide Gironi. I managed to get filtering working using this workaround and all is good except 1 issue. ADGV (and probably all other filters) seems to be designed to filter data ALREADY LOADED to the control, whereas I would like to use it to determine the rows to be fetched from Web Api. Don't get me wrong, I'm able to load chosen records - I'm sending filterstring to Web Api and I'm getting back proper rows. So it's more about creating appropriate filterstring. The thing is, the Excel-like filters let user choose only values already loaded to ADGV (please check the screenshot illustrating what I mean), whereas I'd like it to show all distinct values for a field.. As far as I understand my options are:
somehow make ADGV show all distinct values: this would require having 2 separate data sources - one for ADGV (e.g. showing first 200 rows) and one for its "propositions" the user can choose from (I mean the control on the screen). I don't know ADGV too well and it's possible it can't be done.
using other control (any propositions?)
creating my own custom control (I'd like to avoid that)
I'm using a property list in the back office.
I have an image as one of the properties, the problem I have is it only shows the content Id in the property list table, this is a really poor UI experince.
In addition one of the properties are a URL, again instead of showing a friendly URL it shows and internal URL, again not a very good UI experince for a content editor.
Is there a way to change this?
I am new to EPI server and though I have come accross some good features, what is kind of disapoiting are elements of the UI, a property list table like this could look much much better than this.
Can I customise it?
I'm facing a very critical issue where I can't persist my data to the server.
I am building a dashboard where the user can create new dashboards and customize existing ones. A dashboard layout will have one or more rows. Each row contains one or more cells which vary in width. Each cell will have one or more widget instances where it holds a reference to a particular widget. So you have data about widgets in another table. And I'm using table storage.
So I have the tables as follow.
Page, PageLayout, Row, Cell, CellWidgetInstance
Widget, WidgetInstance
So I have models for all the above tables and added a store for getting a particular page layout.
Page HasMany PageLayout
PageLayout HasMany Row
Row HasMany Cell
Cell HasMany CellWidgetInstance
CellWidgetInstance HasOne WidgetInstance
WidgetInstance HasOne Widget
So I can build the entire view or the edit view modes of the page using the pageLayout returned from the store. So I can access to the Rows collection and go on to the lower levels.
Now the problem comes when I'm trying to save the changes. In the edit view user can add/remove rows, add/remove/update cells, add/remove WidgetInstances etc.
And if the user wishes to click cancel after doing all these changes it should not go to the server and I should be able to reject all the changes in different levels. And if the user wishes to save I should be able to save all the changes in one transaction.
I hoped by adding all the necessary CUD (create/update/delete) proxies to the models, doing pageLayoutStore.sync() and pageLayoutStore.rejectChanges() would do the trick calling each model's create/update/delete urls as per the changes. But it seems although sencha supports retrieving the whole hierarchy it does not support saving as a hierarchy still.
So I'm now hitting a major blocker where I can implement the functionality I needed which is a very standard functionality in most cases. Saving/rejecting models and associated models.
I spent hours searching the web and the sencha forums and all they say is sencha still does not support saving associated data. And in one case there was a work around to save the models then and there without using the store. But in my case I can't do this as the user might cancel after editing.
Can anybody suggest a work around for this?
Many Thanks,
Dushan
You're absolutely right - Sencha does not support saving a nested document.
There are a few workarounds. The simplest one is to use the 'auto' type, at the top level, and give up the power of models the rest of the way down.
A slightly more complex version is to use a custom writer to your PageLayout class, so that it can construct the data to be sent by hand; this will give you full control, and allow you to save your models at the PageLayout level.
It's also possible to extend Model to allow for additional association types - I've done this for my current project, but it's somewhat complex (and, no, I'm not in a position to share it at this time). If you've only got one "top-level model" to save in this nested fashion, then the custom writer is the easiest.
In CakePHP I have a layout created and named default.ctp. In that layout I have a sidebar with some blocks and there're some statistics taken from the database.
My solution: I just created model called Sidebar.php and there're some functions, then I set up data in controller to display it in layout. Is this the best solution? As far I know, I will have to re-set every data in every controller, so need suggestions how to solve that.
Bear in mind that this is coming from a 10,000' level - I know nothing of your particular circumstances, but IMO it's not the best solution. I say that because you've created a model that represents a presentation component. If it were me, I'd probably look at using an element for display. Displaying dynamic components gets a little dodgy, but can be done without violating the MVC "covenant".
Your models should represent your domain entities (you've mentioned nothing about what your stats represent, so I won't offer any specific examples), not how they're presented.