x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 77 subscribers
  • Views 2169 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
RBC

Save not working on custom entities in 2019R2

SUGGESTED
Posted By

Hi

I'm having a problem that has only reared it's head since upgrading to 2019R2 where the 'save' on custom entities either errors with 'Invalid DateTime value' or just does nothing (looks as if it's saving but just stays on the entry screen). There are no date fields set as required on the entity...

Just to make matters worse this is intermittent and a log off/log on allows the user to add new records.

The strange thing is that if you set the user to be a system administrator the problem seems to go away. I've checked the security profiles but cannot seems to resolve, not wanting to leave the users with full admin rights.

Any ideas?

  • 0

    Roger

    Does this show in the logs as an error?  I would expect there to be some trace within either the sql log or the system log. And does this occur to n the simplest of pages?

  • 0

    Hi Jeff

    The weird part about this is that the asp page is the one created by the Entity Wizard (2017 version) but even with the CRM logging set at it's highest values there is nothing being captured in the log files.

    It is happening on 3 'basic' entities BUT there is another entity that was created with workflow and as yet the issue has not been seen when creating records for this!?!?

    Two of the entities are children of the custom entity with workflow but the 3rd is a 'standalone' entity

    To further complicate matters the user whose rights were upped to system admin encountered the issue, so it doesn't appear to be security rights.

    I have a full copy of the system and have spent hours trying to generate this problem without success.

    With reference to the logging, I assume that when the 'datetime error' is displayed CRM is performing a client side check and you wouldn't expect the logs to capture this but when you save and see the browser refresh icon twirling you would think that it is doing something but the affected users are recording the time this happens and I then check the logfiles to find nothing... They logging out of CRM and back in to remove the issue and can run for minutes or hours without it reoccurring (they do not close the browser).

    No changes to the system or processes since the upgrade from R1 to R2 but this issue has only reared its head since the R2 upgrade..

    Thoughts are back everything up, re-install R1 and recover to see if is really an R2 problem BUT I think the risks associated with this would make it a last resort.

    Another day of trying to recreate...

    Thanks

    Roger

  • 0

    An update... I have finally managed to recreate in my test system... I login to CRM, go to an Opportunity and add a Contract record (custom entity with workflow), then add a ContractProduct to this... At this point the 'Save' doesn't work and I'm just left on the entry screen.

    I have captured the following in the system log:

    Oct 17 2019 11:05:11.414 5516 5420 3 CoeWareBaseInit,QueryString copr_contractid=107513&SID=190192236139694&Key-1=58&Key0=58&Key2=318346&Key7=250933&Key27=10533&Key37=107513&Key50=173163&Key58=107513&F=ContractProducts%2FContractProducts.asp&J=ContractProducts%2FContractProductsNew.asp&E=ContractProducts

    Oct 17 2019 11:05:11.446 5516 5420 5 Please enter in values for required fields: cont_productid

    Oct 17 2019 11:05:11.446 5516 5420 5 Please enter in values for required fields: cont_styleid

    Oct 17 2019 11:05:11.446 5516 5420 5 Please enter in values for required fields: cont_materialid

    Oct 17 2019 11:05:11.446 5516 5420 5 Please enter in values for required fields: cont_typeid

    Oct 17 2019 11:05:11.446 5516 5420 5 Please enter in values for required fields: cont_paymenttype

    Oct 17 2019 11:05:11.446 5516 5420 5 Please enter in values for required fields: cont_vat1

    Oct 17 2019 11:05:11.446 5516 5420 3 CoeWareBase,Time 0

    Oct 17 2019 11:05:11.680 5516 5420 3 CoeWareBase,Time 265

    The interesting part is that the required fields are from the parent Contract record not my ContractProduct….and are all populated.

    Log out and log back in, navigate to my contract and I can add/save a contractproduct????

    The SQL log file for this time period is:

    Oct 17 2019 11:05:06.857 5516 6948 3 execsql,time,sql 15 UPDATE Activity SET Acty_UpdatedDate = '20191017 11:05:06', Acty_LastAction = '20191017 11:05:06' WHERE acty_SID='190192236139694' AND acty_UserID = 44

    Oct 17 2019 11:05:06.857 5516 6948 3 fselectsql,time,sql 0 SELECT TOP 51  type_TypeID, type_Name,type_materialid FROM Type  WITH (NOLOCK)  WHERE (type_Name LIKE N'%' ESCAPE '|' OR COALESCE(type_Name, N'') = N'') and type_materialid = 89 and type_Deleted is Null order by type_Name

    Oct 17 2019 11:05:11.461 5516 5420 3 fselectsql,time,sql 0 select cont_Name from Contracts  WITH (NOLOCK)  where cont_ContractsID = 107513

    Oct 17 2019 11:05:11.461 5516 5420 3 fselectsql,time,sql 0 select prdc_Name from Product  WITH (NOLOCK)  where prdc_ProductID = 19

    Oct 17 2019 11:05:11.477 5516 5420 3 fselectsql,time,sql 0 select styl_Name from Style  WITH (NOLOCK)  where styl_StyleID = 37

    Oct 17 2019 11:05:11.492 5516 5420 3 fselectsql,time,sql 0 select mate_Name from Material  WITH (NOLOCK)  where mate_MaterialID = 89

    Oct 17 2019 11:05:11.492 5516 5420 3 fselectsql,time,sql 0 select type_Name from Type  WITH (NOLOCK)  where type_TypeID = 201

    No idea on how I fix this …..

  • 0

    Now for the interesting part.... I've backed up the database and custom pages. Re-installed 2019R1, restored the database and custom page and cannot replicate the problem.. Aaarrgghhhhh…...

  • 0

    Just an update... Sage support have replicated the issue and are investigating....

  • 0
    SUGGESTED

    In case any other readers are encountering this issue, this has been logged with QA, reference: 741-171920-QA.

    If you wish to discuss this defect with support, please ensure to include this reference.

  • 0 in reply to Scott Charlton

    Same Issue - Save not working on primary custom entity in 2019 R2. Any update?

  • 0 in reply to Scott Charlton

    Same issue here as well. Could you give us an update on this issue?

*Community Hub is the new name for Sage City