On 2011-12-07, at 2:17 PM, James Cicenia wrote: This is way old skool/noxymo app. It will be converted next year. And I have been running a custom QueryPage, to custom propertyKey picker, to listPage with button to a POI export to Excel.
I was just trying out ERExcelLook in this app.... In my other wonder D2W apps, it works like a charm! Anyway, I will go back to my old design.
Anyway..... in my propertyKeys list array, I put in the fake ones... so I guess it thinks it is a key path off the EO and barks at me.
Could you please spare a rule sample you used with non-EO Properties off the EO?
You can have properties named whatever you like if they don't exist in your model, but I am not sure what a non-EO property OFF the EO means. Below is an example that Max used to display a link. Not sure what you're trying to display and whether the display is dependant on a value or not. If so, maybe the method to calculate the value needs to be in the EO class (not the model).
( entity.name = 'Movie') and (propertyKey = 'dummy') => componentName = "D2WCustomComponent" ( entity.name = 'Movie') and (propertyKey = 'dummy') => customComponentName = "LinkToViewReviews" ( entity.name = 'Movie') and (propertyKey = 'dummy') => displayNameForProperty = "Number of Reviews"
Thanks James
On Dec 7, 2011, at 4:08 PM, David Holt wrote: The way I have used the ERExcelLook framework in the past has been to provide a button on a list page that downloads the same list to the desktop as an Excel file. The user verifies the result set before downloading.
I imagine that custom reporting that you are talking about should take place on a query page that leads to a list page.
Your results page is then a list that you can display and provide as a download.
Is this what you're imagining?
As for your non-EO properties, if you set up your rules correctly, you should have no issue** returning components that display them. Though if it comes from a keyPath as you're showing below, why wouldn't you use that??
**All this, provided it works without Wonder.
David On 2011-12-07, at 2:00 PM, James Cicenia wrote: Granted this isn't Wonder. However, I can use my old patterns if EXExcelLook can't be integrated..
Anyway, what I wanted to was create a sort of custom reporting system. I need to find the values of individual to-one relationships based upon a qualifier of sorts.
Each project can have N number of metrics. So I thought I could just add a propertyKey... say... "primarySOW"
This is not in my EO per se, the value comes from say project.alignmentMetricForKey(String key); In other words, the key would be "primarySOW".
I wrote a custom component that would use the key to return the proper value.
Just trying to figure out how to wire it up.
Regards, James
On Dec 7, 2011, at 3:53 PM, David Holt wrote: What is this "failed" experiment?
The app will do whatever the rules do whatever you tell them to do. There's no magic.
How about giving us some information we can work with?
Rules? Stack trace? Anything??
What are you trying to do? If you have the list page, why can't you use it in ERExcelLook? Are you sure this will work without Wonder? Seems unlikely to an outside observer.
David
On 2011-12-07, at 1:42 PM, James Cicenia wrote: OK -
I was able to generate a standard D2wList. Still working the Excel part.
Anyway, my experiment proved wrong. I hoping the rules would intercept my "fake" property key and direct it to my custom component.
I didn't want to add these properties to the EO.
Do I have to?
James Cicenia
cell: 773.398.4649
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|