Shraddha Jain

We encountered an issue along Demand forecast lines that when data is being uploaded for 1 budget model (eg: RE 100) and after saving it if we are uploading other data for another budget model (eg: RE 200) then the data in 1st budget model (RE 100) is getting completely replaced and if we check the 1st budget model (RE 100) then it becomes blank with no data at all. However, the new uploaded data appears in new budget model (RE 200).

After reviewing the backend, it was found that the data entity being used for this process is ForecastDemandForecastEntryEntity, through which the data is imported into D365 F&O.

The primary key, or unique identifier, for this data entity is ForecastEntryNumber. Therefore, if the line number in the Excel file is not changed, the system will not delete the forecast lines but will instead update the existing data. This is because the system recognizes that the line number corresponds to an existing entry and will treat it as an update, not a deletion.

Upon reviewing, it was observed that the RecId remains unchanged when the data is imported after modification under a different model. As this behavior is aligned with the current design of the standard data entity, the system works as expected. In the current design, if the user modifies an existing line without changing the line number, the system assumes that the user is updating the existing data.

For adding new data, the user should enter a new line number for the new data as per the current design.