Kinetic custom fields on new Order Lines are not blanking out

Kinetic ERP
, ,
1

We have a customization on our Order Entry >> Lines screen and right now, when we add a second, third, etc. line after the first line is filled in, the screen appears to copy the values in the custom fields, but when you save the line and refresh, there is no data in those fields. It almost seems like the screen fields are not getting initialized on the new line, but don’t have real data in them to be able to be saved either. Any help or suggestions on this would be greatly appreciated.

2

How are you initializing these custom fields? Also, I’m assuming they are custom UD fields that you have added to the order detail table. Is the first line saving the custom fields?

3

Are you working in classic or Kinetic? Are you sure they are bound to an EpiDataView / column? That sounds like the behavior you’d get if they were not actually bound.

4

@r0lovic,

Sorry for the slow response. Work has been crazy the last few days and we lost 2/5 of our IT staff about 2 weeks ago.

  1. I am not initializing the fields as I didn’t know that they would need initialized. I never had to do this in 10.2.200.40. Is there a particular way of doing this for the Kinetic browser?

  2. Yes, they are custom UD fields that have been added to the OrderDtl table.

  3. No, this is not the first line saving the custom fields. This is after saving the first line, then adding a new line and the data appears to copy from the first line, or previous line if greater than line 2, but doesn’t actually copy any data. It appears to be text in the form fields, but not actually in the database.

5

@dr_dan,

This is in the Kinetic web version. We are Public Cloud. Yes, the fields are bound to the EpiDataView / column as when you change the value of the field and save or change it back to the same value and then save, then it will save the data to the database.

6

OK. I am a novice when it comes to Kinetic customizations. I am with you, it sounds like if you have them bound to the correct column, I’ve only ever had it just work. Sorry I can’t be of more help.

7

They don’t necessarily need initialized. I was just curious if you were pre-populating any data in the UD fields when creating a new line. That might have pointed to a custom event that might not be working properly. I’ve done a lot of UD/form customizations in the last year and a half and know that this issue could be caused by a few different things. First thing is first.

  1. Did you regenerate the data model after you added the custom UD fields to the OrderDtl table?
  2. Did you restart the application pool on the server after the regenerate?
  3. Are you adding the lines directly on the “lines” grid on the order detail page or on the lines detail page?
  4. Have you put your browser in debug mode and inspected the dataview in question before and after the add/save?
  5. Are you using any custom events to save the data?

I’ll add a couple of UD fields to the OrderDtl table in my test system just to make sure there isn’t a bug.

We are on the very latest version of Kinetic. 2024.1.8

8

Basically here is all I did to test this:

  1. Go to UD Column Maintenance and added 2 UD field (a string and an int, UDString_c and UDInt_c).
  2. Stopped the application pool for that app server.
  3. Ran regenerate data model for the database attached to that server.
  4. Started the application pool for that server.
  5. Went back into UD Column Maintenance to verify the table and data model were in sync.
  6. Created a new layer based on Erp.UI.SalesOrderEntry and added my 2 UD fields (UDString_c and UDInt_c) to the end of the order lines grid on the order details page.
  7. Saved, committed, and published the layer.
  8. Tested the layer and the UD fields saved properly whether I tabbed through filling in the line values or filling them in on the grid and clicking the save icon at the top of the page.
  9. For an extra test, I went back into the layer and modified the line detail page and added two text fields and bound them to OrderDtl.UDString_c and OrderDtl.UDInt_c, added a new line and verified they saved on that page as well.

That’s all there is really to it. Keep in mind that Kinetic layers sometimes do become corrupted, so you may very well have the correct code, but you might have a bad layer. I would recreate the test above just for a sanity check. Happens to me all the time. :joy:

9

So, ultimately, this stems from not using the Default setting on the Reusable Combo. I am manually setting up the Reusable Combo as we use the CodeDesc for all of our database values and not the CodeID. I found this out on a support call with Epicor Support. I need to provide all of the steps and settings I’m using to Support and they are going to submit it to Development as a possible bug. I haven’t had time to do this yet, but wanted to at least update everyone on what I found so far.

10

SOLUTION:

So, the ultimate issue was I was using the “DropDownStyle” instead of the “DropDown” for the Drop Down Style under Advanced when setting up the settings for a Combo Box. Hopefully this will help someone else.