Picture in your collective conscience if you will an information element with 2 inputs Amount1 and Amount2; both of type 'money' both mandatory both have default values applied at element definition level. One of these is classed as a hot default. . .One link exists with no specific overrides to these values. . .Trying to run a test API load (for one eligible employee) for that element such that we want to have the resulting entry to show the relevant defaulted values. . .Result ? The error message 'Amount1 must be supplied'. . .Anyone else come across this? . .Alternatively has anyone successfully loaded entries of this type?

Clive . .Are you passing null in for amount1 and amount 2 hoping that the definition will provide the values or are you setting amount1 and amount 2 to the defaults ??

I am indeed passing <null> for the inputs - if I explicitly supply the default value then I am overriding the default with a specific value. This of course is not necessarily a problem for the bog-standard default but hot defaults will not take effect where there is a non-null value present. . .Effectively what I want is for the element entry api to behave in the same way as the element entry screen - wherein if I just create the entry and do nothing else the resulting element entry values will contain the appropriate default/hot default values.

Understand para 1 .Agree with para 2 . .I wonder how the app knows that a value is a default. . .I know when you look at a 'hot default' value in the apps screens it is either in red or brackets or something. . .Have you actually tried putting in values I understand the override bit but just wondered what happened ? . .Other than that...sounds like a bug !!! can't beleive that !!!

Yep tried putting in values that reflected the defaults. Of course they were loaded successfully. However when you look at the resulting element entry the value that is meant to be a hot default is not in quotes and red ink. More importantly when one date-tracks to a date beyond which the hot default value changes there's no change to the element entry value. . .TAR is still open...

Quick update on this - the workaround is apparently to null-out the matching input name where there is a null value. Slightly tedious but seems to do the job. Bug no 3403628 btw.