• shabuthomas
  • NEWBIE
  • 0 Points
  • Member since 2008

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 4
    Questions
  • 1
    Replies
I have a visual force page which is having a controller extension.
Edit button of the corresponding object has been overrided in order to display this page on editing.
I've added a button to insert some records in to some other object.
When clicking this button, the corresponding action method in the controller is not called !.
 
Would you please tell me the reason ?
 
Rgds
Shabu
Would you please help me to display Notes & Attachments on a Visual Force page having CUSTOM controller ?
Is there any tag for it ?

Requirement: I have created a record (ID:ax.....01) for object 'Test' with the values for three key fields field1, field2 and field3 as 'aaa', 'bbb' and 'ccc'  (I've explicitly fixed this key so that there should be only one record for this combination key). Then I have deleted it. Again, I have ceated the same type of record (ID: ax.......02). Then, I'm going to undelete record in the  recycle bin (Id: ax......01). This yndeletion should not be allowed as I've recreated the record with same values.

What I have done: In after undelete trigger, I 've queried all records from Test (with out using ALL ROWS, just normal query). Surely, it will contain records with ID ax.....01 and ax.....02. But, since the combination key for both records are same, I've thrown an exception and undeletion was not allowed.

Problem of current implementation: If I undelete more than one recordof Test and undeletion of one record won't result in duplication and but the undeletion of other record will cause duplication, my implementation should not allow both undeletion.

What I need: In after undelete trigger, I should be able to differentiate the records recreated after undeletion.

Problem of ALL ROWS: Even if my organization's recyle bin was empty, when I tried to query all records using ALL ROWS, it showed all previously PERMANENTLY deleted records. So I could not differentiate the intended undeleted record.

Would somone please comment on this ?
Requirement: I have created a record (ID:ax.....01) for object 'Test' with the values for three key fields field1, field2 and field3 as 'aaa', 'bbb' and 'ccc'  (I've explicitly fixed this key so that there should be only one record for this combination key). Then I have deleted it. Again, I have ceated the same type of record (ID: ax.......02). Then, I'm going to undelete record in the  recycle bin (Id: ax......01). This yndeletion should not be allowed as I've recreated the record with same values.

What I have done: In after undelete trigger, I 've queried all records from Test (with out using ALL ROWS, just normal query). Surely, it will contain records with ID ax.....01 and ax.....02. But, since the combination key for both records are same, I've thrown an exception and undeletion was not allowed.

Problem of current implementation: If I undelete more than one recordof Test and undeletion of one record won't result in duplication and but the undeletion of other record will cause duplication, my implementation should not allow both undeletion.

What I need: In after undelete trigger, I should be able to differentiate the records recreated after undeletion.

Problem of ALL ROWS: Even if my organization's recyle bin was empty, when I tried to query all records using ALL ROWS, it showed all previously PERMANENTLY deleted records. So I could not differentiate the intended undeleted record.

Would somone please comment on this ?
Hi,

I have created an Object called Daily Diet. It holds the information of daily diet of a patient. It has following fields:

Patient - Master
Date - Date
Diet -Lookup
Food Item - Lookup
Consumed Quantity - Decimal

Eg: Mark - 12.10.2008 - Breakfast - Biscuit - 5  => Daily Diet ID 1 (Name Field)
      Mark - 12.10.2008 - Breakfast - Tea - 1 => Daily Diet ID 2

Currently, if I add new record with the same values, it will be simply added
    Mark - 12.10.2008 - Breakfast - Biscuit - 6 => Daily Diet ID 3

Similarly, if I change Tea to Biscuit in record 2, it will be like 
Mark - 12.10.2008 - Breakfast - Biscit- 1=> Daily Diet ID 2

So, I have three records with same data. How can I prevent it ?
  • October 28, 2008
  • Like
  • 0