[12.0][IMP] edi_storage_oca: Allow files with duplicate names to create Edi Exchange Record #1127
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ack files should be treated as incoming records. Receive files is not handled yet by the framework and will be added soon.
* A cron job check related storage on edi backends to create the needed exchange files. * Add basic receive component.
…all runtime fixes.
…filenames from storage. Also extend help in `exchange_filename_pattern` field to clarify usage.
Name contained redundant information like type name and related record. On for and tree view is totally useless. To still provide information on linked resource name the 'related_name' field has been added.
When trying to get done/failed directories, if we don't found it on SFTP server, we ignore the error. Current implementation only ignores FileNotFoundError, but depending on the SFTP server, we can have OSError.
By setting specific storage path on exchange type advanced settings, we can configure specific path for each exchange type (input or output). Path can also be configured by config parameters to allow to easily set different values depending of the environment.
Skip 'output_sent' records by default. Reason: most of the times when a message is sent out you don't care about its state anymore. Any subsequent update from outside should come with a new input record instead. Yet, if for any reason this feature is required you can still enable it by passing 'skip_sent=False'.
Currently translated at 100.0% (21 of 21 strings) Translation: edi-14.0/edi-14.0-edi_storage_oca Translate-URL: https://translation.odoo-community.org/projects/edi-14-0/edi-14-0-edi_storage_oca/es/
Enable any internal user to trigger creation of EDI records without EDI Manager group nor read access to storage.backend
Pin 3.1 to fix OCA#1084
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on: