SPLENDIDCRM is an outstanding open source Customer Relationship management system in the. NET environment. At present, there is less information about Chinese, and there are not many content on the official website for two development. Combined with the relevant data found in the network and its own practice, the following take a new module of the development process as an example, the SPLENDIDCRM under the two development steps and the relevant attention to the local description as follows, for peers and interested reference.
1, create a table, such as the need to customize the field, but also to create a _cstm end of the table, such as a many-to-many relationship, but also to create a relational table.
Tables typically contain the following fields: ID (primary key), DELETED (delete flag), created_by (creator), date_entered (input time), modified_user_id (Modify user ID), Date_ MODIFIED (modification time), ASSIGNED_USER_ID (specified user ID), TEAM_ID (Team ID).
_cstm typically contains the following fields: Id_c (primary key).
2. Create stored procedures for updating and deleting data.
Stored Procedure name: SP Module name _update, SP module name _delete.
Then call _devtools/procedures.aspx to automatically generate the code file that invokes the stored procedure SqlProc.cs, which is located under _code and then overwrites the SqlProc.cs file in the _code/dblevel directory.
3. Create a view: At a minimum, include a core view, a view that ends with _list and _edit, and the view generally begins with VW.
4, call the stored procedure spmodules_insertonly to the system to add new module information. This stored procedure parameter description:
Procedure dbo.spmodules_insertonly
(@MODIFIED_USER_ID uniqueidentifier– modification has a user ID
, @MODULE_NAME Nvarc Har (25) – Module name
, @DISPLAY_NAME nvarchar (50)--The display name of the module, described in terms
, @RELATIVE_PATH nvarchar (50)--The directory where the module is The relative path
, @MODULE_ENABLED bit-whether this module is enabled, can also be changed by the system Management->
Studio-> "Configure module" feature
@TAB_ENABLED Bit-whether to display this module on the menu, or to change this property through the system Management->
Studio-> "Configure Modules" feature
, @TAB_ORDER INT--The order that is displayed on the menu, and can also be managed by system- > Studio
-> the "Configure module" feature to change this property
@PORTAL_ENABLED whether bit– is displayed on the portal flag
, @CUSTOM_ENABLED bit-whether or not to The user customizes the field (the table that needs to be _cstm
)
, @REPORT_ENABLED bit– whether the flag for the report is enabled
, @IMPORT_ENABLED bit-flags that can be imported into the data
, @IS_ADMIN bit----whether only the administrator uses the flag
, @TABLE_NAME nvarchar (30) – the table name corresponding to the module
)