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

Custom Model mapping to Embedded Schema won't work until they are in a specific package #107

Open
reynoldbhatia opened this issue Jun 13, 2018 · 1 comment
Labels

Comments

@reynoldbhatia
Copy link

The custom model that maps to an embedded schema has to be in a package com.sdl.webapp.addon.model.entity in a custom module. If not it will not display the content of the embedded schema and will not show any errors in the logs as well. This seems like a limitation that was suppose to be removed in the 2.0 version. The documentation doesn't specify this anywhere.

For more information, please check out this link
https://tridion.stackexchange.com/questions/18962/embedded-entity-not-getting-the-data-from-the-cms/18964?noredirect=1#comment24640_18964

dxa-team pushed a commit that referenced this issue Jul 27, 2018
…10289 to develop

* commit '47c75ea2e3ddd30e2e5f7c4cc580b9037e568188':
  CRQ-10289 rolled back jenkinsfile change
  CRQ-10289 Fixed spring bean initialization for linux box (TridionCacheConfiguration configuration)
  TSI-3249 > Replaces MSBuild steps with powershell ones, cleaned up a bit
@rpannekoek rpannekoek added the bug label Dec 18, 2018
@rpannekoek rpannekoek added this to the v2.2 milestone Dec 18, 2018
@rpannekoek
Copy link
Contributor

Internal Issue ID (for tracking purposes): CRQ-12811

@rpannekoek rpannekoek removed this from the v2.2 milestone Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants