-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide v11 / CAMT 54 File Import #142
Comments
As first step I would suggest to not directly start the import. Instead press the corresponding process button after and initially setting the attachment as "file to to be processed". This way we don't mix it up with the default attachment functionality. |
yes, got your point. do you think we can still make it drag and drop cause its pretty cool? |
or... we can implement some hook mechanism which identifies that we are taking about "v11 import file" and asks the user if we wants to import it. But this feature shall be ADDITIONAL to #144 wdyt? |
instead of ContentType metasfresh/metasfresh-webui-api-legacy#142
…ext values i.e. when resolving context variables if not found we shall fallback to context document #142
note to IT:
|
[#2218](#2218) User would like to import default values for contact and address [#2245](#2445) Support quantity in flatrate term import [#2361](#2361) Invoice Candidates Action Approval for Invoicing [#2387](#2387) Autocomplete for zip / postal code and city [#2298](#2298) Introduce source-HU to fine-Picking [#2247](#2474) Extend Partner Import with ad_language [#585](metasfresh/metasfresh-webui-api-legacy#585) Lookup validation rule shall support @CtxName/Default@ annotation [#2459](#2459) shipto and billto contact / user [#2436](#2436) Use default values for IsShipTo and isBillTo when importing bpartner [#2457](#2457) Duplicate locations on partner import when multiple contacts [#2463](#2463) Extend Partner Import to support contact flags [#142](metasfresh/metasfresh-webui-api-legacy#142) Provide v11 / CAMT 54 File Import [#2429](#2429) hide qty TU when HU name is empty [#2423](#2423) fix jaspers for vendor return with quality issue [#2430](#2430) Invoice candidate close is retrieving the invoice candidates out of transaction [#547](metasfresh/metasfresh-webui-api-legacy#547) Provide mass export of Data to Excel [#570](metasfresh/metasfresh-webui-api-legacy#570) clicking print on non-document window shows error page [#2431](#2431) Product Filter in Handling Unit Editor [#2413](#2413) Make request status a search field in request window [metasfresh/metasfresh-parent-legacy#14](metasfresh/metasfresh-parent-legacy#14) Look for a way of not having the "placeholder" on local builds [#178](metasfresh/metasfresh-webui-api-legacy#178) Have Letter Feature in Sales Order Window [#2401](#2401) vendor return with quality discount [#2434](#2434) Make field ad_user_incharge_id from C_Flatrate_Term optional [#2397](#2397) Import and Store Contract meta-data e.g. startdate on flatrate [#2412](#2412) OrderCheckout Jaspers display empty C_BPartner_Product.ProductName [#582](metasfresh/metasfresh-webui-api-legacy#582) Cannot invoice disposal's invoice candidates [#1060](metasfresh/metasfresh-webui-frontend-legacy#1060) Locale viewing and editing in User Interface [#583](metasfresh/metasfresh-webui-api-legacy#583) Provide the document's standard actions [#581](metasfresh/metasfresh-webui-api-legacy#581) API to provide user session's locale me-45
Results of IT
NOK 1) NOK 2) |
hi @metas-rc |
fixed NOK2. |
Results of IT2: |
allow dragging a v11 file into an esr import and start processing it as if I had used the process "v11 importieren"
The text was updated successfully, but these errors were encountered: