DoctorPolski

Hey vikpaw, In this case that won't be needed as the report will be run via the CLR via an account with the relevant credentials. But thanks as ever for everyone's input. [OT] How do you get the [ mention ]***[ /mention ] tags to work? At least on my message previews I see just an @ with no text after it.

@number34 I've just had Assessment Operator added to my list of privileges and I now get the same list as you and can run precisely the report I need too. Thanks again.

@number34 that is exactly the kind of thing I expected to see. However, when I access the Assessment Results sub-report I only see Aspect and Resultset details which are the last 2 items on your list. Probably a permissions issue?

Hi Guys, Is there a simple way to get a list specific aspect results out of the general SIMS reporting mechanism, ultimately by the CLR? Ideally in a Student focussed report I would like to include the results for a number of specifically named aspects from the assessment manager. I can't find any obvious way to do this. I would like to be able to specify the aspect name at run time which would be supplied from a script elsewhere which I have done for other reports. I can't even find an obvious route to this via a new report based on a focus from the assessment manager list. I've tried looking at Resultset, Gradeset, Result and Aspect but as usual with SIMS it is completely unintuitive. Maybe I see this as a simple task in my head - get the results of specified aspects for all the students in a student focussed report - but apparently it is not. Can anyone at least point me in the direction of what documentation or walkthroughs or tips might be helpful? For example I couldn't find any way to produce the aspect name filter from this post 113407-how-would-you-do-sims-gurus from @LosOjos. Any thoughts gratefully received. Polski

I tried it with the "T" in the format of the datetime as per the xml and all other variations of ' and " and it simply does not work. The file generated by /paramdef doesn't even show the format like it does for every other filter I have used. In short I agree that the "date between" field is broken for CLR.

Hi vikpaw, yeah I'm hooked already. I'm using a different filter now. Rather than the bugged "Active" filter I'm now using a combo of "Start date"/"End date" to achieve the same goal. It makes the pseudo query much more complicated but achieve the same result. How and where would I report such a thing to Capita? If it is part of the usual laborious escalation process I shan't bother. Code bugs ought to be referred from web devs like me straight to the coders at CCS.

Right I have a result!!! Thank you for trying that report, I'm glad it's not just me that it fails for. What I wanted was a record of all the group memberships that were active during the given date range. This will be further enhanced by filtering on pupil name or similar to limit the result set. What I have done to achieve this is split the filter into 2 and asked for (pseudo query clause): (all memberships started before the later date) AND (all memberships ended after the earlier date) That basically gives me all the group memberships that are active during the date window. This is what the Active filter does within SIMS but fails on through the command line. Given the mess it outputs for the filter using /PARAMDEF on the command line and the fact it won't read back I'm going to go out on a limb and say this is a bug in CommandReporter for that filter at least. Thank you so much for help LosOjos. Also very glad I have discovered EduGeek.

OK here is the report: Timetable_Members_2.zip Good luck.

Yep the report runs as expected in SIMS, I can easily check it's working by supplying and earlier start date and seeing 5 more lines in the onscreen output. The parameter ID is definitely correct, I check it every time with /PARAMDEF everytime I even look at the report design. Now, on the window to modify the filter there is no option to "accept all" although I have seen that elsewhere. Interestingly when I run the report from within SIMS the pop-up window that asks you to supply the dates does have that option underneath but it is not checked. The thing is though, the only way I can get the report to run with the default dates from the report is to change that True to TRUE. Otherwise my output contains xml schema for the output but no records.

Thanks again mate. This is the full contents of my params.xml file: Active DateRange Active during 2011-09-06T00:00:00 2011-09-19T23:59:00 It represents my best shot at this. I've changed DateRangeRange from the /PARAMDEF output to DateRange as I agree that makes sense. I did even try changing to so it matched the /PARAMDEF output but to no avail. I have used the datetime with and without timezone, I have removed all the tabs so it is one unbroken line. I'm not sure what else I can try. Thanks for your continued help though.

Thanks LosOjos, it's good to know the parameter ID can be set then forgotten. I have a little progress I think. Here is my param file: Active DateRangeRange Active during 2011-09-06T00:00:00+01:00 2011-09-20T23:59:00+01:00 I have tried it with and without the timezone addition in the DateTime fields but it made no difference. The interesting thing is highlighted in red. When this value is set to ALL CAPS I get the output as if I was running the report without prompting at runtime, that is to say using the default dates in the report. If it is "True" as per the /PARAMDEF then I get no output at all, well I get the output file schema but with no actual data. Does that mean that having all caps is rejected and so it goes with the value in the report? If so and if "True" is correct then it must be trying to use my parameter but somehow failing. I am using a param file rather than supply an xml snippet on the clr. That way I can edit the file and test. If it matters the parameter is supplying the "Active during" filter/clause for Group Membership (Historical). The report allows 'active on' which reqires a single datetime field or 'active during' which requires 2 datetime fields.

Thanks for the response vikpaw. I read through that thread you linked, it came close but not close enough. None of those examples used a type of DateRange which it *appears* from the inline schema of the /PARAMDEF file I need to use. As it seems you may have already discovered if you don't have the "prompt at run time" ticked then the generated param file has no mention of that particular element at all. Having "prompt at run time" ticked gives the example in my first post which just has an empty element. I have no choice but to supply dates in the report designer on SIMS so there are default dates in there. The parameter type of "DateRangeRange" is what is generated by the CLR with /PARAMDEF. I have tried it with just "DateRange" to no avail. Any thoughts on the parameter ID? This changes if I change the default dates in the report designer so how can it ever be correct in my params.xml when it is read back into clr? Am I right in thinking that I need to sign NDA's and stuff just to get documentation for the CLR which is a part of the SIMS software we already license and use in school?

First post incoming.... I have a SIMS report that runs successfully from within SIMS and I can run it from the command line and generate a params file for it. My intention is to change the dates for a certain bounding parameter dependant on values entered into another script. This parameter is a filter clause and is set to "Prompt at runtime" for just this reason but even so the report requires me to enter 2 "default" date values for 'Start' and 'End' dates. The generated paramsfile has 2 issues for me: The XML is not fully fleshed out by including the "default" start and end dates and therefore requires checking of the schema and/or guesswork in order to create the required XML. The parameter ID seems to be dependant on the information entered into the clause in the report and I have no way of generating a new one. For example changing either of the "default" dates or the prompt text causes the ID to change. Here is the relevant part of the paramsfile as generated using CommandReporter with the /PARAMDEF switch: Active DateRangeRange Active during [color="#FF0000"][/color] You can see the blank element is where I hoped the "default" dates would be. Using the inline schema I reckon the fully fleshed out version with example dates should look something like this: Active DateRangeRange Active during [color="#0000FF"] 2011-09-01T00:00:00 2011-09-20T23:59:59 [/color] However, with the completed params file sorted and saved as above and read back in by the CommandReporter this section seems to get ignored and the report runs with the date values which are stored in the actual report. Either the format of the element is wrong or the parameter ID is now wrong. If the element is wrong how do I find out what the correct syntax should be? If the parameter ID is dependant on the contents of the parameter as some sort of encoded hash how do I generate it? My feeling is that the structure is right but the ID is now wrong but any help here would be very gratefully received. Thanks in advance, Polski