Can someone tell me what’s the point of having this check box in the customization tools if it can’t actually control read only in the grid or not? I want to control the field with the epicombo that I put at the top of the page (that works fine), or make the grid a drop down. So the easiest way to do this should be to make the column in the grid (only) read only. Hey there’s a box for that! But when you click it, it reverts back to the extended properties value. But if I make the extended properties read only, it’s read only everywhere.
I was in the middle of trying that out when you gave me the code for drop down, Which is a better solution anyways, so I’m going to use that. Thanks,
But I still think that my point is valid that buttons and check boxes that don’t do anything the customization tool box is annoying at best.
I’m going to set the second answer as the solution, because, technically, it does answer the question. But I ended up using the first because it’s a better solution. It works great by the way. Thanks for the code that I probably should have just googled.
This was covered in some detail in the Insights extended ed sessions. What I’m going to describe below probably doesn’t answer your question, but it hopefully explains the behaviour.
There is a need for the tickbox in Customisation Properties, and it does work in some circumstances. The thing to understand is that anything with an EpiBinding will behave according to the EpiDataView - as you’ve observed, set the EpiDataView to ReadOnly and all controls that reference the field will inherit that property. This is by design. To “break” the link, remove the EpiBinding. Then the field will behave as per properties sheet. Any custom controls that you’ve added which aren’t databound will be configured using the property sheet.
Sorry to bump this topic. Im trying to use the proposed solution to enable a field in Quote Entry screen (Line->Worksheet->Worksheet tab) that I think should be as default, since the same field is enabled on the Line->Detail tab. Im referring to the QuoteQty.SellingQuantity field. The code runs fine but seems that Epicor overides it still. Any thought? Using 10.2.200.26. Thanks
I’m customizing our Order Entry form with a UD table. I used the customization wizard to create the bulk of the initial code. Perhaps I shot myself in the foot doing this. I’m attempting @josecgomez solution but it’s not working as I don’t have a Initialize_Row event.
I’ve been trying to set the column read only in the wizard created events but getting no where it seems.