Colours in functions

htdave

I am trying to setup a kanban for ordering parts.

I would like the kanban tiles to change colour, depending on wether the part has been ordered.
I have a Boolean Attribute "is_ordered"
and a colour attribute "colour_order"

I have written a frontend function to change the colour of colour_order, when the is_ordered status changes:

if (app.get_field_value({F6: 0 ordering.is_ordered}) == true)
{app.set_field_value({F9: 0 ordering.colour_order}, 123 );
} else
app.set_field_value({F9: 0 ordering.colour_order}, 0 );

However, I am not sure on the correct formatting for the colour.

I can make the function change the colour, however, when the user saves the form, the following error occurs:

failed to encode args[0]: unable to encode 123 into text format for varchar (OID 1043): cannot find encode plan

Am I going about all this the correct way, or is the a better way to change the colour of individual tiles?
What is the correct way to define a colour in a function?

Thanks

gabriel

Color attributes use 6 character RGB hex values, so valid values would be 'FFFFFF' or '123123'.

htdave

Thanks Gabriel.

I had tried hex values earlier, but it wasn't working - I had missed the apostrophes either side.

I now have it saving colours correctly.

Is there a way to use this colour attribute to set the colour of each individual cell in the Kanban view?

If I add the colour attribute to the kanban columns, I just get a square of colour, which takes up more space on the kanban tile.

I know I can change the colour of an entire column, but I want to change the colour of each individual cell - Either the background colour, or the top colour, where you drag the cell.

Thanks again for all your help

gabriel

Unfortunately the Kanban field does not support applying colors to individual cards titles/backgrounds, besides adding colors to the card content itself (as you already found out).

This is currently no way around that.

htdave

gabriel Thanks.

At least I can stop trying to work out how to change it.

Is this something that is likely to change in future releases?

gabriel

Not in the near future as we´ve already had to cut back for the next release and have many larger changes to implement for the version after that.

That is one of the downsides of being an open-source company where money comes in from fewer organizations - to pay the bills, we need to highly prioritize requests from paying customers.