Business Process Required Floating Point field needs to be > 0.0 ?

(0) Share

Report

Posted on by ChrisWatson

I have a floating point field (defined as an optional field in the schema) placed in a Business Process Flow stage and marked as a 'required field' in the BPF. When no value specified, the field reads 'click to enter' and if I try to move to the next stage, this (rightly fails). However, it still fails if the value entered is zero (0.0). Any number > 0.0 will allow the process to move on. Zero is a valid value and used to work prior to our upgade to Dynamics 365.

Is this a bug? Does anyone know how to work around this.

Many thanks.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

What happens, when you enter a value greater than 0 and save the form.

Now enter 0, save the form.

Move to the next stage.

Was this reply helpful? Yes No
ChrisWatson 65 on at

Like (0)

Report

Thanks for your reply. The situation is the same whether the values are entered into the form fields or the fields in the process ribbon. Incidentally, the field definition is 'optional' with a minimum value of 0.0 so the problem is not in the domain/range for the field itself either.

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

Hi Chris,

did you try it with another field? Just so you know, I tried a new entity, new BPF - floating point field works without issues (Dynamics 365, online trial).

Wondering if it's the update that went wrong and converted that 0 minimum to something slightly different (like 0.0001)

Maybe try adding your entity to a solution and exporting it, then go to the customizations.xml and see what the minimum is.

It can still show up as 0.00 in the user interface if it's slightly more than that:

If that's what the problem is, either fix it directly in the file and reimport the solution.. or, maybe, it will work if you simply switch that minimum to 1, save, publish, then back to 0.. directly in the UI..

Was this reply helpful? Yes No
ChrisWatson 65 on at

Like (0)

Report

Hi Alex,

I did as you suggested and the output is as follows:

<attribute PhysicalName="cpc_PackingTime">
<Type>float</Type>
<Name>cpc_packingtime</Name>
<LogicalName>cpc_packingtime</LogicalName>
<RequiredLevel>none</RequiredLevel>
<DisplayMask>ValidForAdvancedFind|ValidForForm|ValidForGrid</DisplayMask>
<ImeMode>auto</ImeMode>
<ValidForUpdateApi>1</ValidForUpdateApi>
<ValidForReadApi>1</ValidForReadApi>
<ValidForCreateApi>1</ValidForCreateApi>
<IsCustomField>1</IsCustomField>
<IsAuditEnabled>1</IsAuditEnabled>
<IsSecured>0</IsSecured>
<IntroducedVersion>1.0</IntroducedVersion>
<IsCustomizable>1</IsCustomizable>
<IsRenameable>1</IsRenameable>
<CanModifySearchSettings>1</CanModifySearchSettings>
<CanModifyRequirementLevelSettings>1</CanModifyRequirementLevelSettings>
<CanModifyAdditionalSettings>1</CanModifyAdditionalSettings>
<SourceType>0</SourceType>
<IsGlobalFilterEnabled>0</IsGlobalFilterEnabled>
<IsSortableEnabled>0</IsSortableEnabled>
<CanModifyGlobalFilterSettings>1</CanModifyGlobalFilterSettings>
<CanModifyIsSortableSettings>1</CanModifyIsSortableSettings>
<MinValue>0</MinValue>
<MaxValue>1000000000</MaxValue>
<Accuracy>2</Accuracy>
<displaynames>
<displayname description="Packing Time" languagecode="1033" />
</displaynames>
<Descriptions>
<Description description="This is the packing time to be included in the costing." languagecode="1033" />
</Descriptions>
</attribute>

as you can see the min value is zero so not sure what is going on here?

Chris

Was this reply helpful? Yes No
ChrisWatson 65 on at

Like (0)

Report

I suspect this might be a bug as doing everything that you have all suggested as well as everything I can think of does not make a difference. Does anyone know how I can get hold of Microsoft or request they take a look at this problem? It is rather inconvenient for our customer to be doing this. Many thanks.

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

Hi Chris,

not sure you can simply do it on behalf of the customer.. you can, but Microsoft will need your client's id to find out what kind of support they are eligible for etc.

I did not have an opportunity to speak to MS support for a little while now, so there could be other ways (for example, if your client has an account manager on the MS side.. you could just ask that person by email to see what's the best way to handle this)..

Anyway, I would probably just go here to start with: www.microsoft.com/.../contact-technical-support.aspx

Was this reply helpful? Yes No