UPDATED: Okay, Rick wins this one with an early correct answer! Definitely an easy one but I was surprised to come across this. Never underestimate ‘schoolboy errors’ creeping in to code! I’ve seen plenty of occurrences of using the assignment operator (=) in place of the equality operator (==) but this was the first time I’d come across it the other way around! Well done to all who spotted the mistake and to everyone who identified other issues in the code. Note that the field was Force Active, I just forgot to tell you. Virtual pints all round, I think!

An easy one this time round. However, as before, this is a genuine coding error that I found in a live Siebel environment! As usual, a virtual prize (i.e. no prize) to the first poster to spot what’s wrong!

function CodeChallenge2(sContactId)
{
  // Declare variables
  var boContact, bcContact;

  try
  {
    // Instantiate new BC instance
    boContact = TheApplication().GetBusObject("Contact");
    bcContact = boContact.GetBusComp("Contact");

    with (bcContact)
    {
      // Create query context
      ClearToQuery();
      SetViewMode(AllView);
      SetSearchSpec("Id", sContactId);
      ExecuteQuery(ForwardOnly);

      // If record is found, update the status
      if (FirstRecord())
      {
        SetFieldValue("Status", "Active");
        WriteRecord();
      }
    }
  }
  catch(e)
  {
    // Call the custom LogError function to write error to error log
    LogError("Woops, an error has occurred!");
  }
  finally
  {
    // Destroy objects
    bcContact == null;
    boContact == null;
  }
}

Answers on a postcard or using the comments box below!

UPDATE: Well done to Ranjith for spotting the error: the RaiseErrorText will itself raise on exception, which is trapped and ignored by the catch statement. As a result, the message that the developer thinks the user will see will be suppressed and never display. Ranjith chose a virtual pint of lager as his reward – more code challenges to follow so more opportunities to win non-existent prizes!

I came across the following code the other day in a live Siebel environment. There’s a free virtual pint to whomever first identifies what’s wrong with this picture!

function CodeChallenge1(sContactId)
{
  // Declare variables
  var boContact, bcContact;

  try
  {
    // Instantiate new BC instance
    boContact = TheApplication().GetBusObject("Contact");
    bcContact = boContact.GetBusComp("Contact");

    with (bcContact)
    {
      // Create query context
      ClearToQuery();
      SetViewMode(AllView);
      SetSearchSpec("Id", sContactId);
      ExecuteQuery(ForwardOnly);

      // If record is not found, inform the user
      if (!FirstRecord())
      {
        TheApplication().RaiseErrorText("Record not found! Try again.");
      }
    }
  }
  catch(e)
  {
    // Call the custom LogError function to write error to error log
    LogError("Woops, an error has occurred!");
  }
  finally
  {
    // Destroy objects
    bcContact = null;
    boContact = null;
  }
}

Answers on a postcard – or use the comments box below!