Is there a new feature in 7.2 where it is tracking Application Rows?
I just recently did a deployment of anything that changed since a date and time… It included an application row "BP_VCS,I_PO_IMPORT_LOG". This row has not changed but a program that uses it as an insert did change.
I guess the question is two fold.
1. Why did it think the row changed when it did not…
2. Is there a way of tracking certain Application Rows? (Controls records etc.)
Thank You,
John
John,
The OI 7.2 compiler was changed to allow better tracking of relationships for stored procedure (and event scripts too)
In your case you have an insert like this:
$insert sometable,somerecThe compiler will come across this and create a relationship between your proc and the APPROW. As this is the first time the compiler has come across this a new APPROW entry is created for the record - this is why it will show up as "changed" in the RDK.
You can also manually link procs to other repository components by using the $USES statement
e.g. If you are using a struct function in your proc and you want to link in the struct definition in you can do something like this:
$uses SYSPROG*APPROW**SYSOBJ:STRUCT_RECTi.e. $uses
Another change in this area was repository tracking via call statements. In previous versions of OI you could only track a link to a subroutine if you declared it before you used it:
e.g.
declare subroutine mySubmySub( var1 )If you did this:
call mySub( var1 )The compiler didn't track the relationship in the repository. Now it does.
Regards
World leaders in all things RevSoft
… one further clarification the compiler repository linking:
$insert - links the APPROW/STPROCINS to the STPROC
$uses - links the specified entity to the STPROCEXE
declare - links the specified entity to the STPROCEXE
call - links the specified entity to the STPROCEXE
World leaders in all things RevSoft
Thanks for the clarification… that really does seem powerful.
One last question. I have a table I use for running procedures. Anytime a row changes in this table I have to remember to manually copy it into the RDK after the fact. Is there a way of adding this to the repository so that it will get tracked and automatically sent in the next update?
Thanks,
John
John,
How about - an MFS that creates an APPROW entity (if not already present) and updates the entity UPDATED field when modified?
You'd catch this in the RDK then.
Regards
World leaders in all things RevSoft
John,
Sounds like you need me to make my PX_MFS work in OI. Just for data rows, though.
Dave
Hi Dave,
I was experimenting with updating the Repository as it will track this in the next RDK. Not working just right yet…
John
Thanks for the idea…
I was just testing this out and have not been able to create the Repository entry yet. I tried Repository("SET", EntID,""). It created the entry but not in the right format. Any suggestions or samples for creating+ updating the Repository for APPROW?
John