This error can be the result of duplicate mapped properties in the search
results section of your search command.
If you are testing the latest builds of Maestro 3.0, it has enhanced Web
Layout validation rules to detect:
- Duplicate command names
- Orphaned menu entries
- Duplicate property m
Thanks, I am able to get the Samples to work correctly as well.
Brian
Brian,
The standard template works for me with the most recent MGOS2.2
release. I am seeing an error with the Google layer now that I will fix.
Mike
On 10/28/2010 9:12 AM, Berdel, Brian wrote:
> I can add tickets for this
In your filter, drop the quotes to your field name, so you should have:
ADD_FULLNAME LIKE '$USER_VARIABLE%'
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Maestro-Layout-Task-frame-menu-search-filter-syntax-tp5100122p5683306.html
Sent from the MapGuide Users mailing l
Brian,
The standard template works for me with the most recent MGOS2.2
release. I am seeing an error with the Google layer now that I will fix.
Mike
On 10/28/2010 9:12 AM, Berdel, Brian wrote:
I can add tickets for this, but before I do I wanted to check if anyone else
has tested fusion
I can add tickets for this, but before I do I wanted to check if anyone else
has tested fusion successfully with 2.2 RC1. I am able to bring my map up with
the install version but I immediately notice that the google base layer is on
the other side of the world and the selection tool is not fun
Thanks for the response, I was able to get it to work by creating a new project
and adding the references to the osgeo.mapguide dlls then pasting the rest (VS
would not allow explicitly adding them as references)
However I am using fusion in my apps and it appears pretty broken at this point
bo
