Change Color of UD TextBox Based On Its Value

[jharrington (James Harrington)]

LOL, okay. I’ll give that a shot! Thanks!

[jharrington (James Harrington)]

I have added the code, tested it, compiles successfully, but does not change the background color.

I inserted the messagebox.show function at the position illustrated below, but it is not firing.

    private void epiTextBoxC1_TextChanged(object sender, System.EventArgs args)
    {
        MessageBox.Show("Text Changed");
        if(defaultTextBoxBackColorIsSaved == false)
        {
            originalTextBoxBackColor = ((EpiTextBox)sender).BackColor;
            defaultTextBoxBackColorIsSaved = true;
        }

[aarong (Aaron Gulley)]

@jharrington

but does not change the background color.

@klincecum

IT’S TIME TOOOO…

[hkeric.wci (Haso Keric)]

Did Row Rules not work? Just use the Wizard under Row Rules Tab and it should get you there. Simple Row Rules will also migrate to Kinetic.

E10.1.600.30 - Strange form behavior

In the Epicor Client, the data controls the UI elements and the Epi-Controls respond to the Extended Properties “metadata” defining both a column and a cell. You do not color a control, you color the data; You do not disable a control, you disable the data. We do this so that any control displaying the data - individual field, Grid, or control added via Customization - will display and managed the data in the same way. Use Row Rules and the UI will behave as you expect.

[klincecum (Kevin Lincecum)]

@jharrington

I have added the code, tested it, compiles successfully

Did you modify it for the correct textbox ?

[jharrington (James Harrington)]

@klincecum

private void epiTextBoxC1_TextChanged(object sender, System.EventArgs args)

epiTextBoxC1 is the correct textbox. Other than the above code, does it need to be updated elsewhere?

[klincecum (Kevin Lincecum)]

Did you use the event wizard to add the event handler?

If not, add this to Initialize CustomCode & DestroyCustomCode:

public void InitializeCustomCode()
{
    this.epiTextBoxC1.TextChanged += new System.EventHandler(this.epiTextBoxC1_TextChanged);
}

public void DestroyCustomCode()
{
    this.epiTextBoxC1.TextChanged -= new System.EventHandler(this.epiTextBoxC1_TextChanged);
}

[jharrington (James Harrington)]

Those two lines of code did the trick! I always forget about the initialize- and destroy- code. I’m still such a neophyte to all of the syntax and rules! However, I have learned a lot from this!

Thank you to everyone that assisted me on this thread. I genuinely appreciate it!

[klincecum (Kevin Lincecum)]

@jharrington

I’m still such a neophyte to all of the syntax and rules!

A long time ago, in a galaxy far, far, away… I knew nothing.

I still know nothing, but I have grey hair in my beard now.

[klincecum (Kevin Lincecum)]

BTW, go look into the row rules, as per @hkeric.wci .

I’ve never used them on anything other than grids, but it should work.

[jharrington (James Harrington)]

What a coincidence, same here!

[Ernie (Ernie Lowell)]

@klincecum

I still know nothing, but I have grey hair in my beard now

Wish it was still just in my beard.

[jharrington (James Harrington)]

So…
There is one more outstanding issue with this customization. Even though I have the custom {QuoteHed.VerStmntStatus_c} field set as ReadOnly (see screenshot), it is not read only and users are able to edit the field. I assume this is because the UseAppStyling is set to False??

Is there a way to force this to be readonly in code?

[klincecum (Kevin Lincecum)]

@jharrington

Is there a way to force this to be readonly in code?

Yes, but I would edit the extended properties on the dataview instead and make it readonly there.

If you search for “extended properties readonly”,
you should be able to find some examples.

[jharrington (James Harrington)]

Thank you Kevin! I’ll have a look.