Interface

As start date, end date and day values are auto populated then please set them in the CDT/ dictionary/ map at the start of your UI, don`t use default value function in the value. Whenever there is a change in the start date or end date recalculate the difference and store it in the day.

Only no of days needs to be auto populate after user selecting the start date and end date

then in saveinto set the value of differnece in case of whenever user set value in any of the date field. 

Apply the below logic on your end date it will directly save the number of days to your rule input.

a!dateField(
label: "End Date",
value: ri!date,
saveInto: {
ri!date,
a!save(
ri!days,
tointeger(tointervalds(save!value) -tointervalds(today()))/*today is your start date*/
)
}
)

I was using a grid field In that the value is not saving

share some reference for your code it should work.

a!integerField(
value: (
if(
a!isNullOrEmpty(
ri!RMS_AddResourceModelContractPricing.enddate
),
{},
(
tointeger(
tointervalds(
ri!RMS_AddResourceModelContractPricing.enddate) - tointervalds(ri!RMS_AddResourceModelContractPricing.startdate
)
)
)
)
),
saveInto: fv!item.demandhours
),

This code for no.of days grid field

Actually you are passing the logic in the value field try to pass the same on the saveInto end date field. Save Into for a field works when you perform some action on that field. 

Use the below code for saveInto of your end date. Value will be saved to your rule input.

{
    fv!item.enddate
    if(
      a!isNullOrEmpty(
        fv!item.enddate
      ),
      {},
      a!save(
        fv!item.demandhours,
        (
          tointeger(
            tointervalds(save!value) - tointervalds(fv!item.startdate)
          )
        )
      )
      )
    )
  }

It's Worked Thanks

The real important thing to learn here is that the "saveInto" parameter of a component does absolutely nothing unless you actually change the value referenced in that component.  Until then, the saveInto will never execute.  That's why if you have a field where all it does is display a calculated value based on other fields, if you actually need that calculation stored somewhere, you need to do the work to save that value in some other location.

The real important thing to learn here is that the "saveInto" parameter of a component does absolutely nothing unless you actually change the value referenced in that component.  Until then, the saveInto will never execute.  That's why if you have a field where all it does is display a calculated value based on other fields, if you actually need that calculation stored somewhere, you need to do the work to save that value in some other location.