-
Type:
Bug
-
Status: Done
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Company:All Clients/Multiple Clients
URL : corporate/dms/api/manageCustomFields/Onboard
ACCDid : A7F0PT78MTMZ470WBBT
UserDid : dmsuserid4cmp1
- is caused by
-
DMS-1850 Add Caching framework in DMS
-
- Done
-
This API is throwing Error after today's build deployment(11/Sep/2019)
PFA -
PFA :
Re-opening this jira
Jayshree Nagpure (Inactive)
added a comment - This API is throwing Error after today's build deployment(11/Sep/2019)
PFA -
PFA :
Re-opening this jira
Priya Dhamande 3C's :
Concern : API is throwing following Error,
{ "status": "error", "message": "Unable to resolve service for type 'DMS_AppLogic.Repository.ICompanySetupRepository' while attempting to activate 'DMS_WebApi.Controllers.IntegrationAPI.CompanySetupController'.", "errorLevel1": "Error", "code": 500, "description": "Unable to resolve service for type 'DMS_AppLogic.Repository.ICompanySetupRepository' while attempting to activate 'DMS_WebApi.Controllers.IntegrationAPI.CompanySetupController'." }Cause : This error was getting due to the code changes missing from Jira DMS-1850 in file 'Startup.cs'
Correction : Added required changes in 'Startup.cs'.
Thanks,
Sonali Farakate
CC : Rohan J Khandave
Sonali Farakate (Inactive)
added a comment - 3C's :
Concern : API is throwing following Error,
{
"status": "error",
"message": "Unable to resolve service for type 'DMS_AppLogic.Repository.ICompanySetupRepository' while attempting to activate 'DMS_WebApi.Controllers.IntegrationAPI.CompanySetupController'.",
"errorLevel1": "Error",
"code": 500,
"description": "Unable to resolve service for type 'DMS_AppLogic.Repository.ICompanySetupRepository' while attempting to activate 'DMS_WebApi.Controllers.IntegrationAPI.CompanySetupController'."
}
Cause : This error was getting due to the code changes missing from Jira DMS-1850 in file 'Startup.cs'
Correction : Added required changes in 'Startup.cs'.
Thanks,
Sonali Farakate
CC : Rohan J Khandave Environment: Preprod and Production - OneIM
API: api/manageCustomFields/Onboard
Verified on both environment. Working as expected.
Refer screen capture. So, marking jira done.
3C's :
Concern : Manage Custom Fields was not working
Cause : Condition for empty fields(section and label) of payload was not handled in code.
Correction : Validated the value of payload fields 'section' and 'label' is empty or not.
Thanks,
Sonali Farakate
CC : Rohan J Khandave