feat: added edit functionality for demand dialog

[Akash-IAV]

Description

resolves #1009

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files
• If helm chart has been changed, the chart version has been bumped to either next major, minor or patch level (compared to released chart).

[Akash-IAV]

Hi @tom-rm-meyer-ISST ,
I have implemented the Edit functionality for the Demand modal, similar to how it works for the Stock modal.
All required fields are set as editable, based on the specifications mentioned in the ticket, and the functionality is working as expected.

However, I’m encountering an issue with the Day field:

• The API response does return a value for day, but for some reason, it’s not being patched into the form when attempting to edit a specific record.
• I’ve already collaborated with a colleague and we’ve tried multiple approaches to resolve it, but the issue persists.

If you have any suggestions or can assist in looking into this issue, it would be greatly appreciated.

[Akash-IAV]

Hi @tom,
We are using : import { DateType, Datepicker } from '@catena-x/portal-shared-components'; for the date and time handling.
After reviewing the Catena-X Datepicker implementation, we noticed that it maintains its own internal state
and only initializes that state from the defaultvalue prop using an internal useEffect. Because of this design, the value prop passed from the parent component is ignored during the initial render.
For ex (current code):
<Datepicker value={date?.toISOString().split('T')[0]} /> does not prefill the date properly on mount, since the component never updates its internal state based onthe value prop.

During our R&D, we observed that using defaultvalue (instead of value ) allows the date to prefill correctly on initial render. It appears that the Datepicker expects defaultvalue for initialization and only becomes responsive to user changes after that.
Below are the changes we applied:
function formatDateYYYYMMDD(date: string | Date): string {
if(typeof date === "string" ){
return date.split('T')[0];
}
const d = date;
const year = d.getFullYear();
const month = String(d.getMonth() + 1).padStart(2, "0");
const day = String(d.getDate()).padStart(2, "0");
return ${year}-${month}-${day};
}

const formattedDefault = useMemo(() => {
if (!value) return undefined;
return new Date(formatDateYYYYMMDD(value));
}, [value]);

return (
    <Stack width="100%">
        <FormLabel>{props.label}</FormLabel>
        <div className="date-time-picker">
            <Box display="flex" gap=".25rem" width="100%" marginTop="auto">
                <Box display="flex" flexGrow="1" sx={{ '& .MuiFormControl-root, & .MuiBox-root': { minWidth: '100% !important' } }}>
                    <Datepicker
                        {...props}
                        error={error}
                        // value={date?.toISOString().split('T')[0]}
                        defaultValue={formattedDefault} --> new Code 
                        readOnly={false}
                        onChangeItem={(event) => handleDateChange(event)}
                    />
                </Box>

I have tested this locally, and it works fine - the date now prefills correctly on initial render and updates properly when changed.
Please review these changes and let me know if you have any additional suggestions or alternative
approaches.

[tom-rm-meyer-ISST]

Thanks for the investigation! I don't see the need for the formatting. Using the defaultValue only works fine in the modal during local test.

[tom-rm-meyer-ISST]

Thanks for your work!

Please merge the feature branch / rebase.

Please recheck your license headers:

• ADD IAV 2025 as copyright holder to changed files.
• ADD only IAV, contributors to EF 2025 as copyright holder to new files.

Some other findings you can see via comments - thanks in advance!

[tom-rm-meyer-ISST]

Thanks for the investigation! I don't see the need for the formatting. Using the defaultValue only works fine in the modal during local test.

[Akash-IAV]

Hi @tom-rm-meyer-ISST,

Thanks for the detailed review and comments. As suggested, I have made the changes and committed them in this branch. I request you to kindly review the updates and let me know if anything further is required.

[tom-rm-meyer-ISST]

Answered comment, checked rest. If you incorporate that small change as proposed, I gonna merge.

sorry for delays. If you're out, please let me know. Then I merge and do the rest myself on the feature branch

[tom-rm-meyer-ISST]

LGTM, thanks a lot!