Adding Activities and History to a Custom Entity in the Saleslogix Web Client (Part 1)

This week I decided to take on the challenge of coming up with some easy to follow steps that will help a developer add the ability to associate Activity and History records for a custom main entity within the SalesLogix Web Client.  The next several posts should provide the reader with the step by step details of how to accomplish the task. 


A couple of items for consideration: 




  • A custom main entity is one that is simular to the Account, Contact, or Opportunity main entities in the SalesLogix Web Client. 


  • This process should not be accomplished on a live working SalesLogix system.  The team here at Customer FX always suggests that modifications to a system be created in a development or test environment.  This allows you develop and ensure the modifications are working without effecting the working SalesLogix system.  Please make sure to establish a development environment prior to following these steps.


  • I wrote this process using a tool called Power2Project, a web based Project Management Tool created by the team at Customer FX for the SalesLogix web client.  Please realize and substitute the term FXProject for your custom entity.


  • To accomplish these modification you will need access and working knowledge of the SalesLogix Application Architect and the SalesLogix Database manager.  Access to Microsoft Visual Studio 2008 is also beneficial but not mandatory.


  • To the accomplished developer, I try to write to lowest level so please bare with me as I get into the weeds a little helping out the lesser experienced.


The first step in adding the ability to associate an Activity and History record to a custom entity is to add the custom entity Id field to the Activity and History tables through the SalesLogix Database Manager (db manager).  This step will allow us to relate the new entity to the Activity and History entities in the web environment.  Adding these fields to the tables has to be done through the db manager because these are legacy tables not built through the Application Architect.  


You can find the db manager in the SalesLogix Administrator or the SalesLogix Architect.  For this example I use the db manager through the SalesLogix Architect, when the Architect opened I clicked on the following icon located on the Architect tool bar.


When the db manager opens, right click on the Activities table in the tree control on the left, you will see the pane on the right will immediatly display the fields for the Activity table, now select the “Create New Field” item from the menu that appears.  The Field Properties dialog will open. 



Fill in the properties for the EntityId field.  Make sure to make the type of field is set to “SLX Standard ID”.


Select “OK” and follow the same procedure for the History table.


When the both the Activity and History tables have the new EntityId field added, find and select the  “Apply Changes” icon located on the Architect tool bar.  Once the update process is complete close the SalesLogix Architect and open the SalesLogix Application Architect. 


In the Application Architect (AA), find the Project Explorer Tab.  As you open the tree control under this tab, find and select the “Entity Model”, then Packages, then “SalesLogix Activity Support”, finally right click on “Activities” and select “Update Properties…” from the list that appears.  The Modify Entity dialog for Activity will appear.



At the very bottom of the list you will find the new EntityId field you entered through the db manager, check the box on the left and select the “Finish” button.  Follow the same process for the History Entity which is also located on the same level in the tree control.


Next, select “Build Web Platform”  icon located in the AA toolbar. 


To get ready for the next step in this process you need to decide which fields from your custom entity will be used in the look up located on the Activity insert and edit pages.  To keep things easy I suggest using fields that are located directly on the entity but if you want to use fields related to the entity through a relationship to another entity it will be important to know the relationship name.  We will use these fields over and over so make a list and have it ready for the next post. 


You can move righ tto the next post by following this link.


 Until then stay safe, have fun, and keep smiling.


 



 

Submit a Comment

Your email address will not be published. Required fields are marked *

Subscribe To Our Newsletter

Join our mailing list to receive the latest Infor CRM (Saleslogix) and Creatio (bpm'online) news and product updates!

You have Successfully Subscribed!