@Alex,

In addition to Width="0" for the column, you can:

• Use an empty Grid column <Template>
• OR
• Use the Grid column's OnCellRender event to set a column CSS class and apply zero font size

        <GridColumn
                    Width="0"
                    OnCellRender="@( (GridCellRenderEventArgs args) => args.Class = "no-content" )">
            <Template></Template>
        </GridColumn>

<style>
    .no-content {
        font-size: 0 !important;
    }
</style>

Of course, a Grid popup FormTemplate is also an option, if you also need other customizations.

Regards,
Dimo
Progress Telerik

Hello all,

We have had very little interest in this, especially considering such functionality can be implemented through the Visible parameter the columns have had for a while. The opener post also contains an example. We have also had no constructive feedback on how else this should be exposed. Therefore, I am marking this as a Completed feature because it is possible and we haven't had better suggestions on how this should be done than our Visible solution.

Regards,
Marin Bratanov
Progress Telerik

Hi Chris,

The Visible and Editable parameters have different functions and they must not get mixed together. The Editable parameter control whether an editor is rendered for the column when it  goes in edit/insert mode, otherwise it shows the current value (or, the EditorTemplate and Template if you prefer to think of this in terms of templates). The Visible parameter controls whether the column is rendered at all. It would be used for responsive designs to hide some columns on smaller screens, and it is also used by the end user to hide columns they don't want to look at through the column chooser in the column menu. Thus, Visible is a user setting, that is tied to UI, and goes in the grid state, while Editable is a developer setting the user cannot interfere with.

That said, I am attaching here a small sample and a short video that show how you can have different columns (fields) in the popup form without a custom popup form and without altering anything in the grid behavior. It is literally a few lines of code - on OnClick handler for the Add button, a handler for OnEdit, and they both simply raise a flag. Then lowering that flag in the other CRUD events and using that flag for the Visible parameter of the special column is all it takes.

Regards,
Marin Bratanov
Progress Telerik

Hi again,

With the upcoming 2.17.0 release, the columns will have a Visible parameter that you can toggle when the grid is in edit/insert mode. I am attaching here a small sample and a video of the expected that shows how that would work. Would that be suitable behavior, or would you expect something else from the grid (we still do not find the that third bullet to be a well-defined scenario for the grid).

Regards,
Marin Bratanov
Progress Telerik

Hello Andrew,

A Visible parameter is likely to get exposed for this one. It would, however, control the general column visibility in both the grid, and the popup. Perhaps you might be able to toggle it in the OnEdit event, but I can imagine this would be rather cumbersome.

That said, how you you expect a parameter to control the visibility of a column in the popup, considering it is not declared in the grid? At the moment, for a column to be visible AND editable in the grid it must be declared. If you set its Editable parameter to false, it won't show up in the popup editor at all (there is also a way to make it non-editable through data-annotation attributes, see here).

So, I can see the following three scenarios:

• you want to both show a field and edit it - just declare a column for it
• you want to show a column but not edit the given field - you declare a column but set its Editable parameter to false
• you want to NOT show a column, but edit its field - that's the scenario that is unclear and we find confusing. How would you expect that to be exposed for configuration?

Regards,
Marin Bratanov
Progress Telerik

Hello Ben,

With a custom edit form you can edit however many fields you like, and you can even switch models as suitable for your app - the grid will not be limiting or controlling that in any way.

To take the example - if you define 3 out of the 5 fields of the model in the grid, you can have the following behavior:

• the built-in popup editing will let you edit/insert those three
• a custom form can let you edit all 5, a subset of them, or an entirely different model

For cases where you want the grid to show one thing, but the user to see another, a custom form is the solution we have - the grid offers API to let you invoke that form with the desired business logic.

Regards,
Marin Bratanov
Progress Telerik

Hi Ben,

The popup shows only the editable fields defined in the grid. If you set Editable=false to a column it won't appear in the popup. The goal is to have a clear visual mapping between what the user sees in the grid and the edit form so they don't get confused.

Also, the grid can be bound to one model - it is used for displaying, inserting, editing and deleting records, and using a different one would pose several major problems - unnecessary code complexity notwithstanding, it will be a breaking change for everyone (including people who don't need or use such a feature), and it will cause confusion for the users to see one thing in the grid, another when editing, and a third when inserting a record.

Thus, at this point we believe that the best way to handle such cases is to use a custom edit form as shown in this sample project https://github.com/telerik/blazor-ui/tree/master/grid/custom-popup-form or in this demo: https://demos.telerik.com/blazor-ui/grid/editing-custom-form. This will let you use whicever models you want in the forms, and have different forms for editing and inserting - the grid allows you to have full flexibility in this regard, while handling the most common scenarios out-of-the-box.

On large models with a lot of fields - the AutoGeneratedColumns can let you do that, and they also let you specify fields to skip and read-only fields: https://docs.telerik.com/blazor-ui/components/grid/columns/auto-generated.

That said, I am keeping this open for a while so we can gather some more feedback on this to see if anyone else wants to see the same thing.

Regards,
Marin Bratanov
Progress Telerik