Skip to content
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

AD_Element_Trl customization #4982

Open
teosarca opened this issue Feb 22, 2019 · 0 comments

Comments

Projects
None yet
2 participants
@teosarca
Copy link
Member

commented Feb 22, 2019

Is this a bug or feature request?

What is the current behavior?

Which are the steps to reproduce?

What is the expected or desired behavior?

  • be able to provide name/description/help customizations which are stored in separate fields
  • don't allow changing regular fields and customization fields

image

@teosarca teosarca self-assigned this Feb 22, 2019

teosarca added a commit that referenced this issue Feb 22, 2019

teosarca added a commit that referenced this issue Feb 22, 2019

teosarca added a commit that referenced this issue Feb 22, 2019

refactor how we react to trl changes
also
* removed the GridTable code and move it to AD_Element_Trl interceptor
* GridTable: always use PO to save to database

#4982

@teosarca teosarca referenced this issue Feb 22, 2019

Merged

Gh4982 #4986

@teosarca teosarca added the bug label Feb 25, 2019

metas-ts added a commit that referenced this issue Mar 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.