Error initializing Dataset on FSM

 Hi ​@afarhat,

I also checked the said baseline “FieldServiceCustBusPolicyMgr.cs” code and it does have a code line for 

 

Make sure in your installation, you have the “Metrix.Threesixty.Integration.dll” file in the following folder, 

“C:\inetpub\wwwroot\<YourServerName>\bin”

And also make sure this perform definition is in the database. Please run this following command and check,

SELECT * FROM metrix_perform_def WHERE perform_name = 'perform_initialize_threesixty'

 

Also, if you have done code level customizations to this “InitializeThreesixty” method, make sure those are properly uplifted and compiled before updating FSM. And check the “Perform Definitions” screen to check if there is a custom perform with the same name “InitializeThreesixty” there. That screen only shows custom performs.

Best regards,
Hushan
 

Thanks Hushan for your fast response, i did run SELECT * FROM metrix_perform_def WHERE perform_name = 'perform_initialize_threesixty'

I got the following result, do you think must be another issue?

Hi ​@afarhat,

• Since it says “Initialize Threesixty(system.string,)” Which to me, looks like that piece of code public void InitializeThreesixty(string datasetIdIn), may be check with your internal team if you have done any code level customizations to “FieldServiceCustBusPolicyMgr.cs” code, and if so, that code file has this public void InitializeThreesixty(string datasetIdIn) method?

• Also were you able to check the “Perform Definitions” screen to check if there is a custom perform with the same name “InitializeThreesixty” there?

• Also, make sure in your installation, you have the “Metrix.Threesixty.Integration.dll” file in the following folder, 

“C:\inetpub\wwwroot\<YourServerName>\bin”

Thanks & best regards,
Hushan

Well, iam not sure if was done any code level customization, i will chck it out by the dev team.

Also checking Perform Definitions screen there is no InitializeThreesixty as down shown:

Hi ​@afarhat,

Please check with your DEV team and if there are such code level customizations, ask them to recompile the DLL. Also make sure that DLL file is in that location. Also please mention the FSM version you are using and if it has been recently updated.
Also, you can try increasing the log levels in Server logs, set TR -7 and EX - 9, and then recreate this error several times and then collect the log, check the stack trace where this error is coming from.

Thanks & best regards,
Hushan