All Comments

You can do this by changing the fields names on the parent side to the real PS fields. That said we are strongly against this. With the approval process the office can validate the validity of the data being submitted. By allowing parents to directly modify your day to day parents could quickly decide to delete all the info you allow them to enter. You would no longer be able to get to the data without doing a restore, and who know just how long that it will take before you even notice. This could also quickly become a liability if your unable to get a hold of a parent in a emergency because the parents chose to delete their info because you gave them a way too. In the end it's a very bad idea to not use a approval process.

How would you disable the approval process for demographic change? I have added other fields to the page which update automatically but the fields on the original demographic change page need to go through the approval process. How do you turn this off as well?

thanks

gail

I'd love to see what this looks like. I'm trying to figure out if this will work for our Athletics department. I am considering using the Special Programs area to track participation in athletics, with the ability to track participation over time. Would this report be able to report on awards given over time or just for the current year?

Dave

Figured this out myself:

1) Added conditional statements to the f.table_info:

condfield3=storecode;condfieldtype3=TEXT;comparator3=.ne.;condval3=P1;
condfield4=storecode;condfieldtype4=TEXT;comparator4=.ne.;condval4=P2;
condfield5=storecode;condfieldtype5=TEXT;comparator5=.ne.;condval5=P3;
condfield6=storecode;condfieldtype6=TEXT;comparator6=.ne.;condval6=P4;]

2) Added to WHERE statement in the tlist_sql:

AND storedgrades.storecode NOT IN ('P1', 'P2', 'P3', 'P4')