WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsHi All,
I'm having an odd issue where the merged configuration XML contains multiple instances of some repeats and fields which should be merged into a single instance, whereas other fields from the same local configuration are working as expected.
I have a tenant config file which merges three additional configuration files into the base collectionobject config
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-excerpt-from-tenant-config-xml
The one I am having trouble with is the last one which only updates options in dropdown in lists:
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-profile-colelctionobject-xml
The merged output can be seen here:
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-colelctionobject-xml-xml
You can see that the numberType field is working as expected:
config file
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-profile-colelctionobject-xml-L5-L21https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-colelctionobject-xml-xml
merged file
And in the UI I See what I expect.
However, the objectNameLevel field is not being merged, but having a second insatnce of <field id="objectNameLevel"> created in the merged XML file
config:
merged file:
instance 1: (with only the base config)
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-colelctionobject-xml-xml-L233
instance 2: (with only the extension config, not merged at all)
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-profile-colelctionobject-xml-L42
In the UI, I only see the terms listed int eh base configuration.
Any ideas on why this is happening? Whay would some merge normally and not others?
Thanks
Chad
Hi All,
Just wanted to let the list know that some help from Richard with a second set of eyes sorted out this issue.
Turns out that the order of <repeat> and <field> elements inside a <section> of an domain/local configuration file must match the order of those <repeat> and <field> elements in the base configuration file you are overriding.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of Chad Nelson chad.nelson@lyrasis.org
Sent: Tuesday, June 16, 2015 4:54 PM
To: talk@lists.collectionspace.org
Subject: [Talk] XML merge creating duplicates fields instead of mergeing them
Hi All,
I'm having an odd issue where the merged configuration XML contains multiple instances of some repeats and fields which should be merged into a single instance, whereas other fields from the same local configuration are working as expected.
I have a tenant config file which merges three additional configuration files into the base collectionobject config
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-excerpt-from-tenant-config-xml
The one I am having trouble with is the last one which only updates options in dropdown in lists:
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-profile-colelctionobject-xml
The merged output can be seen here:
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-colelctionobject-xml-xml
You can see that the numberType field is working as expected:
config file
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-profile-colelctionobject-xml-L5-L21https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-colelctionobject-xml-xml
merged file
And in the UI I See what I expect.
However, the objectNameLevel field is not being merged, but having a second insatnce of <field id="objectNameLevel"> created in the merged XML file
config:
merged file:
instance 1: (with only the base config)
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-colelctionobject-xml-xml-L233
instance 2: (with only the extension config, not merged at all)
https://gist.github.com/bibliotechy/085bfeffa7e3c54df869#file-fcart-profile-colelctionobject-xml-L42
In the UI, I only see the terms listed int eh base configuration.
Any ideas on why this is happening? Whay would some merge normally and not others?
Thanks
Chad