back to top

Posting changes from a Telerik RadGrid row edit back to a bound SalesLogix entity

More on the Telerik RadControls for ASP.Net AJAX- they really really rock

The more I work with them the more I really love them.  Thanks to some feedback from their support department I have figured out how to perform an automatic update of whatever fields changed when editing a RadGrid’s data row back to the SalesLogix entity on which they are bound.  I will be posting a lot more on specifics about how to bind SalesLogix entities to these controls, how to do CRUD operations, etc.

Today I want to focus on how to perform an update on a RadGrid’s row edit event to update the bound SalesLogix entity.

First you need to get a reference to the Telerik.Web.UI.GridEditableItem of the passed in Telerik.Web.UI.GridCommandEventArgs from the RadGrid’s update command like so:

 

Telerik.Web.UI.GridEditableItemeditableItem  editableItem= ((Telerik.Web.UI.GridEditableItem)e.Item);

Next, using this object, you can fetch the primary Id of the edit row (assuming that you have bound the Id as the primary key of the row):

string rowId = editableItem.OwnerTableView.DataKeyValues[editableItem.ItemIndex][“Id”].ToString()

 

With the row ID fetched, we can now instantiate a reference to the underlying object like:

 

Sage.Entity.Interfaces.IAccount account = Sage.Platform.EntityFactory.GetById<Sage.Entity.Interfaces.IAccount>(rowId);

Then we make sure we actually have a valid record:

if (account != null){}

 

 

Finally inside this if block we add the simple, elegant, and totally awsome single line of code to take the RadGrid row’s edited properties and update our referenced entity with them:

editableItem.UpdateValues(account);

 

And last we call the Save event to post our entity changes back to the database:

account.Save();

And in total here is the code:

Telerik.Web.UI.GridEditableItemeditableItem  editableItem= ((Telerik.Web.UI.GridEditableItem)e.Item);
string rowId = editableItem.OwnerTableView.DataKeyValues[editableItem.ItemIndex][“Id”].ToString()
Sage.Entity.Interfaces.IAccount account = Sage.Platform.EntityFactory.GetById<Sage.Entity.Interfaces.IAccount>(rowId);
if (account != null)
{
    editableItem.UpdateValues(account);
    account.Save();
}

 

How totally cool is that!?

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Kris Halsrud
Kris Halsrud
Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos