Skip to Content

This is a continuation of Part 1, here.

So far we have:

  • Created a Global Solution in the FP3.5 Studio
  • Enabled Key User
  • Created an extension to the Customer BO and added some extension fields
  • Created a new BO with Customer ID, and the extension fields to serve as a staging table
  • Added an AfterModify script to the staging BO that will move the staged data to the Customer BO
  • Created a XML File Upload Service Integration to load data to the staging BO, activated it, and downloaded the .xsd file that is generated upon activation

Let’s finish this thing up!

Open up Excel and in your Developer tab click Source and add that .xsd file.

Now that you have the XML structure in place, you must, and I mean MUST, do two things.

The first is to drag the CreationDateTime element to the top of the Excel file as you see below. I don’t know why, but you’ve got to populate the date to look like this: 2012-05-25T12:00:00.000Z. Weird!

The second thing you MUST do is drag the entire List of your BO’s elements into the Excel sheet. Don’t ask me why. JUST DO IT, OK?

Now you can delete the columns no one cares about. (BTW, the default value for actionCode is Save, so that’s why you don’t need it in this case)

Now populate your spreadsheet with the stuff you intended to migrate during your implementation, but sadly forgot to.

In the Developer tab, export the XML to somewhere.


Then go to Application and User Management, and choose the File Input view. Select Unprocessed Files in the OWL. Upload that XML document and specify the Service Interface we tossed together earlier.

Next, create a Run for this Service Interface in the Active Runs OWL. Save it. Activate it. Close it. Schedule it to run immediately. Monitor the process and notice that it has completed successfully. Love it when that happens.

After all that, you need to enhance the Customer screen to show your extension fields.

Choose the item checked below. It’s the standard ByD Account screen. Trust me on this one.

Select the Details pane, then add the extension fields!

Save and activate the UI. We’re almost done! After that, go into Account Management and select Edit > General for any of our staged customer.

WHOA! Look at the details pane! It’s got our fields, populated with the data we entered!

This is just one example of a post-implementation mass data load. There are possibilities for many more.

In order to see the results in reports, you would need to create a new Data Source on the Customer BO extension, then go into Business Analytics and join it to an Account Data Source. I may cover this in a follow-up post, but for now, rest assured your extension fields contain data.

Imagine creating extension fields as a Key User, then having to manually enter data into thousands of screens. I’m pretty sure the solution here is far superior.

Should you have questions or need help with with a similar situation, leave comments, email me at jwickham@bramasol.com and/or follow me on twitter @JudsonOnDemand.

Have a great long weekend!

To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  1. Angel Perez

    Hi Judson, thanks for this tutorial, it’s great

    I’m learning about ByD studio and I get into trouble following this tutorial.

    The problem comes when I’m trying to create Service Integration, I can see all possibilities: create screens, create Query, Script Files… all of them, except Service integration. Also I can only use the type of solution: Customer-Specific Solution.

    I understand there is more types of solutions.

    The questions are:

    1. Service integration can be seen only from Add-on solution?

    2. If I can only use customer-specific solution, how can I get another kind of solution? Maybe someone have to assign me to one specific WoC in ByD? or can you tell me a hint?

    Thanks in advance

    Angel.

    (0) 
    1. Judson Wickham

      Angel,

      You will not be able to do this in a customer-specific solution until FP4.0.

      Instead, you’ll need to create a web service to do the mass load. You do that in the Studio.

      – Judson

      (0) 
      1. Angel Perez

        One more question, do you know a possible reason because I can’t choose another type of solution? I only have “customer-specific” in Studio …

        Thanks again.

        (0) 
  2. Vineet Narayan

    Hi Judson,

    Thanks much for the detailed article. Very helpful blog.

    I have a question about one of the steps, if you can please advise…

    The ‘actionCode’ value defaults to ‘Save’ (04) when we don’t provide it. But if I want to ‘delete'(03) or ‘remove'(05) the data in the input file (after having inserted earlier ofcourse), I would provide that in the file, just like providing the CreationDateTime value, correct? I did that, but the record is not getting deleted or removed from the list in UI…

    I tried adding the ‘actionCode’ as a column in the list of BO elements also, but in that case, am not able to export the xml at all, so I am assuming we have to give actionCode as a value ‘outside’ the list…

    Is there something I am missing..?

    Thanks,

    Vineet.

    (0) 

Leave a Reply