Timeline for MetaData exception duing creating new component using core service
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 24, 2015 at 12:47 | vote | accept | Chakresh Singh | ||
| Jul 24, 2015 at 12:31 | vote | accept | Chakresh Singh | ||
| Jul 24, 2015 at 12:47 | |||||
| Jul 24, 2015 at 11:27 | answer | added | David Forster | timeline score: 2 | |
| Jul 24, 2015 at 11:14 | history | edited | David Forster | CC BY-SA 3.0 |
deleted 21 characters in body
|
| Jul 24, 2015 at 11:12 | history | edited | Peter Kjaer | CC BY-SA 3.0 |
Code formatting
|
| Jul 24, 2015 at 11:10 | answer | added | Peter Kjaer | timeline score: 4 | |
| Jul 24, 2015 at 11:08 | comment | added | Chakresh Singh | When I check original component meta data schema in CME manually it's really 'embedded_global' not 'embedded_workflow'. But I unable to debug why core service retruning metadata schema as 'embedded_workflow' | |
| Jul 24, 2015 at 11:02 | comment | added | Andrey Marchuk | Just to double check, the schema is the same, right? Is the original component valid? Can you open it, edit and save, edit metadata in particular | |
| Jul 24, 2015 at 10:58 | history | asked | Chakresh Singh | CC BY-SA 3.0 |