I have tried to follow the Tessitura Custom Screens document as best I can but I'm obviously missing something here. Any help here is greatly appreciated I'm trying to create a tabular datawindow in the Performance Details Custom Tab and while it appears correctly inside tessitura there is no update/edit ability. My custom table has been created as below. I have added update/add/select/edit rights to the ImpUsers group. I have added ID_key as the primary key The only retreival arguement supplied in the datawindow is for the :inv_no
I'm trying to create a tabular datawindow in the Performance Details Custom Tab and while it appears correctly inside tessitura there is no update/edit ability.
My custom table has been created as below.
I have added update/add/select/edit rights to the ImpUsers group.
I have added ID_key as the primary key
The only retreival arguement supplied in the datawindow is for the :inv_no
The data in the sql select is primarily found in tessitura tables and then left joined to the custom LT_AMT_PERF_CUST_TAB to retrieve existing values or act as placeholders for the user to modify in Tessitura. Does my custom table need to be populated in advance, if so how do I populate the ID_key which is primary? I thought the datawindow supplies this ID_Key value at run time. Is there an object in the Security module that controls this datawindow? I am only seeing the existing PE Tabs and no reference to the custom one i have created. Thanks for you time! -doug
Does my custom table need to be populated in advance, if so how do I populate the ID_key which is primary? I thought the datawindow supplies this ID_Key value at run time.
Is there an object in the Security module that controls this datawindow? I am only seeing the existing PE Tabs and no reference to the custom one i have created.
Thanks for you time!
-doug
TR_CUSTOM_TAB
Hi Doug,
Good day.
select * from t_next_id where type='CT'
The id_key is populated by datawindow, so you should not set it as primary key.
You can have another id as primary key and identity field, this can avoid duplicates in custom table. Duplicates are very easy to happen.
Every time you insert a record datawindow will populate a id_key, when you select a record you need id_key and customer_no, when update a record datawindow will pass the id_key.
so id_key is half controled by you, and half controled by datawindow.
if you want to update the IM custom tab, it has a lot limitations, it can only update a table not a view.
You have to point directly to the table not a complicated view.
If you know how to develop a intranet site, I suggest you use a intranet web page as a custom tab instead of infobreaker.
A year ago, I faced same problems with IM. it cannot do this, it cannot do that.
So you can have two choice:
1, using IM, then you should use the custom tab for display only.
if you want to insert or update a record, you can use CSI + SQL job to update the target table. (this is in our custom tab now.) it will be a bit complicated. You need to look after t_cust_activity.
2, use intranet as a custom tab, you can do anything you want to.
have fun.
Ben
Wow I mangled the subject line here...thanks for deciphering my post Ben.
Yes infomaker is so strange sometimes. I had to downgrade so I think I was also having an issue due to the datawindow that was originally built in 10.5.2.
I did end up sticking it out in Infomaker and was able to properly setup the custom table to house all my data (protecting the fields that we don't want updated). Joining to any other table besides the custom update table in the DW's datasource did not work like you had said so it seems like no other option other than to house in the custom table every column that you want displayed on the tab.
Funny though is that I am using id_key as primary and have not had any issues and my sql job to populate this custom table is using and incrementing the value in t_next_id properly. Time will tell.
Hyperlinking the customer#, order# at first appeared to be a problem since the NOEDIT tag needs to be used here but to hyperlink you have to use ID_CONST(customer_no). There is another protect property also in infomaker which allowed me to use the hyperlink and prevent user editing of the customer_no and order_no fields.