Tag: Entity Model

In this first article on using the Model class I'll be showing how to get the schema of an object. The model class in the DevKit SDK is the new API for working with entity data in Freedom UI pages. Previously in classic Creatio pages, you'd create EntitySchemaQuery objects to query data, InsertQuery to create new records, UpdateQuery to...

Along the same lines as my previous article covering referencing entities using the IDynamicEntity interface to set and get properties by a string name instead of as a strongly-typed object, you can also use the IComponentReference interface as a generic entity type since all entities implement this interface. This interface is found in the Sage.Platform.ComponentModel namespace and is why...

There might be times when you need to set an entity property value by the property name as a string at runtime. Sure, you could use reflection for this and use the PropertyInfo class, but there is a built-in way that is much easier to use. All entities implement the IDynamicEntity interface, which provides this functionality out of the...

When using IQueryable to look for records within an Entity collection you will likely run into an error at some point when trying to add a condition to search for when that condition is a related entity property, or is a calculated entity property.For instance, lets say we have the Sales Order entity that has had a calculated entity...

Using external assemblies in SalesLogix development, rather than built in Code Snippets, is a better & more efficient way to customize SalesLogix entities, with far less headaches. Some of the benefits include a better and more complete development environment and having all your code in one place (instead of digging around through all the entities to get to the code). Let's take a look at how to do it.

For some who have been working in the SalesLogix LAN client for years, the transition from using SQL queries to retrieving data using a repository with the entity model can be a difficult change. This post will look at some common data retrieval methods and the SQL equivalents to help you get your head around how to get work done using the entity model.

The SalesLogix entity model offers a really great way of working with data in SalesLogix and letting the system establish all of the links for you- as long as you know what you are doing. One of the really great things that you can do is to add child entities to a parent, even if the parent is not yet in the database. This is especially helpful if you need to create child records while still on an insert screen.

I have not found any official reference to this change anyplace: prior to 7.5.2 the Sage.Entity.Interfaces.IOwner entity contained a RightsCollection collection of user rights (Sage.Entity.Interfaces.IOwnerRights which represents the database table SECRIGHTS).  In 7.5.2 this has changed to now just be called Rights.  If you have any code that was using the previous property name “RightsCollection” you will need to...

It is useful at times to be able to programatically determine at runtime if a user has read access, write access, or no access to a particular field at runtime. There are many different ways this information can be used to ensure you're giving the current user the best, and most understandable experience based on that particular user's security settings allow for. Luckily, with the introduction of the FieldLevelSecurityService in SalesLogix 7.5 this is an easy task. Let's take a look.

One of the keys to reusing a form for both inserting new records and displaying existing record detail is the ability to determine if the form is currently in insert mode or detail mode. There are several ways to determine this at runtime so you can take the necessary steps depeding on the current form mode.