WAD: Change scaling factor of more then one structure_members

Question

Hi,
why does this command doesn't work?
<SAP_BW_URL DATA_PROVIDER='MP_CO503_FAKTVO'
CMD='SET_VALUE_PROPERTIES'
STRUCTURE_MEMBER_1='ECZELC2Q4KXX0JB5X544SY821'
STRUCTURE_MEMBER_2='EH8UVZZWVCF9AVOACGJ6HLIDL'
SCALING_FACTOR='0' DECIMAL_PLACES='1'>
the command works fine only with STRUCTURE_MEMBER_1. by adding STRUCTURE_MEMBER_2 to the command, the whole command doesn't work.
please help.
thanks.
Edited by: Pascal Kühnis on Apr 7, 2010 11:57 AM

Answer 1

Ahhh, sorry for the confusion. What you need are "Collections". If you click the "Review Demonstration Applications" link then install the "Collections Showcase", this should give you a good working sample.
Collections are comprised of an HTMLDB_COLLECTIONS package and an associated table. Use the package for creating a collection and adding members (rows) and use the table to query what's in your collection.
Essentially, here's what you need to do. Let's assume your multi-row form is on page one and you have a confirmation page on page 2:
- Create a process that fires on submit of page one that uses create_or_truncate to create your collection.
- In the same process, loop over your collection items and add them (as members) to the collection.
- Make sure your multi-row form queries from the collections view. This way if you go to page 2, then back to page 1, you will see your rows. When you go to page 2 again, you can just over-write the existing collection. There's another option, but I'll list that later.
- Create a process on page 2 to loop over the collection view and insert the rows into a table. Make this conditional based on the button you press, such as "Save".
- Extra credit: Either the collections package or the htmlb_utilities package as an md5 function. You can call this when querying the data out of the collections table, then call it again as you are looping over the data on submit. Basically, you are checksumming the row on the way out, then again when the page is submitted. If the 2 are equal, the data is unchanged. If they are not equal, the data has changed. Based on your needs, you can use this technique to insert / update records. I have an app that uses this technique because I have a before update trigger on the table that I only want to fire if the user actually updates a particular row.
Hope this helps,
Tyler