Removing empty photostream events

Since upgrading to 10.8.1 iPhoto is displaying events for every month since I turned on PhotoStream, even if the photos have all been moved elsewhere. The resulting events have the blank Sunset with palmtrees image and contain no photos. Is there a way to hide or remove these Events?

Sorry... I was at work and didn't have the version number in front of me... 9.3.2 I have a little over 17,000 photos in this Library (1 of 8) in 72 Events.
I tried draging one Event over another a couple times and they came back. This afternoon I used the Merge command from the Menu, Moved the resuting empty Even to the Trash and Emptied the Trash. After Quiting the program and reopening it, they did not return.
Aperature 3.3.2 is sharing this Library and when I just opened Aperature, they all came back.
This started when I updated the System to 10.8.1

Similar Messages

How do you sort your Photostream Events in iPhoto?

I have my photostream photos automatically imported to iPhoto on my iMac - so I have lots of "events" with names like March 2013 photostream or July 2014 photostream. In each of these events, there are often a whole group of photos that belong together - like a birthday party. There are also some "one off" photos that just one or two shots of something I wanted to photograph (like a couple of pictures of a rainbow, or a picture of a recipe that I like to have on hand so that I can shop for ingredients). I am not sure how these are supposed to be handled. I can leave them all in photostream and add key words to the photos so that I can search for them perhaps (but then I have to manage a lot of key words. I cannot just add a key word "Birthday Party" since I attend many birthday parties. I would have to use a key work like "Bob's 30th birthday party" unless I wasted my search to turn up every picture ever taken at any birthday party!) i can create an event and call it "Bob's 30th birthday party. That seems to work ok - although I'm not sure if I should be doing this. As for the other photos, like the two of the rainbow and the one of the recipe, I don't know what to do with them. I can leave them in photostream with keywords. I can create an entire event called "Recipes" although the range of dates on such a folder might be quite wide since I am always saving recipes, which means that when my events are sorted by date, my new recipes will appear in an early event along with the very first recipe I ever took a photo of!
I would love to know how others arrange their events . Do you ever create an event based upon a subject (My Cat Missy) even if the photos span a good deal of time? Or do you leave Missy's photos spread over many events depending upon what date you snapped the photo??? Have you ever completely emptied out a monthly photostream event (for example, let's say all your photostream photos for the month were taken at one wedding, so you moved them all into a single event called "Kate's Wedding."
See what I mean? Back in the windows days, when admittedly, I took fewer photos, I would create a folder for each big photo taking event (christmas, weddings, birthdays, a lovely walk in the park) and I would create just one folder with the year "Photos from 2008" to put in all the ones and twos photos that don't really belong with anything else. I also had a single folder with pictures of my cats and one that had photos of recipes. I added to these photos anytime I had a picture of my cat or a recipe to upload.
What does everyone recommend? Sorry for being so long winded. I cannot find any info on "how to sort or manage monthly photostream event photos" so perhaps I am the only one with this issue.

1. There is no right answer. There is no "should". There is the way that makes sense to you.
2. You can keyword photos with Birthday party, but also Title them with Bob's 30th, that gives you two ways to search for them
This might give you some ideas:
I use Events simply as big buckets of Photos: Spring 08, July - Nov 06 are typical Events in my Library. I use keywords and Smart Albums extensively. I title the pics broadly.
I keyword on a
Who
What
Where basis (The When is in the photos's Exif metadata). I also rate the pics on a 1 - 5 star basis.
Using this system I can find pretty much find any pic in my 50k library in a couple of seconds.
So, for example, I have a batch of pics titled 'Seattle 08' and a typical keywording might include: John, Anne, Landscape, mountain, trees, snow. With a rating included it's so very easy to find the best pics we took at Mount Rainier.
File -> New Smart Album
set it to 'All"
title contains Seattle
keyword is mountain
keyword is snow
rating is 5 stars
Or, want a chronological album of John from birth to today?
New Smart Album
Keyword is John
Set the View options to Sort By Date Ascending
Want only the best pics?
add Rating is greater than 4 stars
The best thing about this system is that it's dynamic. If I add 50 more pics of John to the Library tomorrow, as I keyword and rate them they are added to the Smart Album.
In the end, organisation is about finding the pics. The point is to make locating that pic or batch of pics findable fast. This system works for me.

Remove Empty XML Tags using module parameters

Hi All,
In my lanscape I have two PI Systems.
My scenario is an IDOC reaches 1st PI system gets converted into an EDIFACT and then goes to the 2nd PI and from there it gets routed to the respective AS2 Party.
I am using SOAP to pass message between the PI systems and B2B Toolkit's AS2 Adapter for the communication with AS2 party.
The issue is when the message is getting converted from IDOC to EDIFACT there are a few feilds with occurence 1..1 and due to these fields i get an empty XML tag at the output. These empty XML tags give me an error in the B2B Toolkit's AS2 Adapter Receiver Channel
I cannot change the occurence in the structure of the EDIFACT nor can I use an XSLT mapping to remove empty tags before the message reaches the Communication Channel.
I want to know if there are any module parameters which i can use either in SOAP Channel or the AS2 Channel to remove the XML Tags.

Hi Muni,
"1..1 means, you must send some values for that fields. try to find out why these are not getting any values."
This empty tag is expected. Before using B2B Toolkit's AS2 Adapter we used to use Seeburger's AS2 Adpater and the message used to get executed successfully with these empty tags.The issue is coming only when we are using B2B Toolkit's AS2 Adapter.
"if you want to stop sending(the fields which are not needed in target) you can you can disable the fields in the message mapping."
I cannot disable the feild in the mapping as some other message may use this field.
Thanks,
Farhaan

How to remove 'Empty Demarcation' in Text Elements.

Dear All,
To remove 'Empty demarcation' in the WAD output, I had modified the standard program - SAPLRSSV (for this i took access key from SAP).
The text element : 301 was changed to blank and it worked.
Recently we had a support package upgrade to SAPKW70018. With this upgrade my previous change to the program got reverted back and so i need to do the change again.
However, I'm not able to retrieve the list of Text elements for this program (SAPLRSSV). I open the program and when i go to Text element, following message is displayed :
"Untranslated texts from master language DE will also be displayed"
But no list (no text elements) is displayed.
My question : How do i retrieve this list and can i use the same acess key again or do i need to take another one from SAP.
Regards,
Nagendra.

Sorry, I was referring to the incorrect program SAPLRSSV instead of SAPLRRSV. The problem has been resolved.
Regards,
Nagendra.

Photostream Events Deleting in iPhoto?

Question on Photostream in iPhoto. I have iPhoto set to automatically import photo's to events and my events appear as separate days in the Events section of iPhoto. I also see one event per month for the Photostream photo's for that month...so November 2013 Photostream for the current month for example. The photo's in the photostream event don't appear in the event for the day the photo was taken....i.e. they are not duplicated in two events....the monthly photostream and day event. I have noticed today that the oldest monthly photostream is October 2012 Photostream. I have ~500 photo's in My Photostream. There must have been monthly photostream events earlier than October 2012 so my questions are -
1. do the monthly photostream events delete from iPhoto after a set period of time even if you have not reached the 1000 photo limit, and
2. if a monthly photostreram event is deleted, are all photo's in the photostream event deleted if they are not appearinmg as separate day events (the event being the date the photo's were taken on) and even though I have automatic import into events turned on?
Thanks
Brian

Welcome to the Apple Community.
Assuming that iPhoto > preferences > PhotoStream > automatic import is checked then yes, photos from PhotoStream are automatically imported into monthly events and are saved even when PhotoStream deletes the photos due to numbers/time restrictions.

FlipTransition raises "Removed from Stage Event" on new view

hello,
I Have a problem with a fliptransistion. If I use this transition in my main view to go to a "settings" view. The "removed from stage" event is raised for the settings view (yes the settings view).
So first the "initialize" of the settings view is executed. In this initialize I hook up some event listeners.
Than the "removed from stage" of the settings view is executed. In this function I remove the event listeners (I think this is a good thing to do).
Than the "removed from stage" of the settings view is executed again
So the event listeners never work.
The code for the transition is nothing special I think
var ftrans:FlipViewTransition = new FlipViewTransition();
ftrans.duration =1000;
navigator.pushView(SettingsView, data, null, ftrans);
When I use the default transition "navigator.pushView(SettingsView, data)" the problem does not occur.
Anybody an idea as to how to solve this (I'd prefer to keep the fliptransition, as the default slide transition is used in another part the application, and the flip indicates to the user that he is doing something different).
Update: I've tried to move the event listeners to the "added-to-stage" phase but this doesn't quite solve the problem the events that occur on the SettingsView are: (in that order!)
- Added To Stage
- Initialize (this is bizar the view is added to stage even before it is initialized).
- Removed From Stage
- Added To Stage
- Removed From Stage
- Added To Stage
Message was edited by: NilsTT

The FlipViewTransition effect does some reparenting internally to accomplish the 3D effect. As a result you receive multiple add and remove events. To work around this, I would recommend using FlexEvent.ADD and FlexEvent.REMOVE instead of addedToStage. You can also try using ViewNavigatorEvent.REMOVING.
Chiedo

[svn:osmf:] 17548: Remove left-over event handler, which could trigger an unnecessary event if a player loaded plugins through the config XML file and manually (e.g.

Revision: 17548
Revision: 17548
Author:   [email protected]
Date:     2010-09-01 14:09:14 -0700 (Wed, 01 Sep 2010)
Log Message:
Remove left-over event handler, which could trigger an unnecessary event if a player loaded plugins through the config XML file and manually (e.g. for static plugins).
Modified Paths:
    osmf/trunk/libs/samples/ChromeLibrary/org/osmf/chrome/configuration/PluginsParser.as

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Remove or Disable Events

I received hundreds of photos from many different photographers each month for publication in a magazine. The date the image was taken is totally irrelevant to me - I need to store them in a folder for the month of publication, ie, June. Later, when I select the 30 or so photos I want to actually use, I have to edit the size and resolution of each separately for 1) print, 2) website, and 3) a newsletter. In all this editing, I've got way too many "events" that I never use and later have to delete. I just want to remove or disable "Events" from iPhoto entirely, so that when I receive an image, I can store it where I want without risking all duplicates I'll have to delete later. How do I remove or disable the "Events" part of iPhoto?

You can not
Events are one view of the contents of the library - by default they are date time based - you can combine events and delete events and change the sort order of events
You also can see your library in Photo view (with or with out event titles displayed) and the photos view also offers several sort options
I would use albums for storing the Photos according to month of publication -- or use a more powerful (and much more expensive) Digital Asset Manager - iPhoto is a consumer program designed for consumers with digital cameras - it is not a full fledged DAM (although it is a darned good one for its target audience) for a magazine publisher
Since you are using it for a purpose it was not designed for you will need to wither switch or adapt
LN

Unable to remove empty nodes from Message

Hello,
I have message format like this:
<?xml version="1.0" encoding="UTF-8"?>
<ns1:Enrollment xmlns:ns1="http://pac.bluecross.ca/Common/Types" xmlns:ns2="http://www.w3.org/2001/XMLSchema-instance">
<ns1:Policies>
<ns1:Policy>
<ns1:Code>11140</ns1:Code>
<ns1:Certificates>
<ns1:Certificate>
<ns1:Class>
<ns1:Code>1</ns1:Code>
<ns1:EffectiveDate>2009-05-09T00:00:00</ns1:EffectiveDate>
</ns1:Class>
<ns1:CurrentEmploymentRecord>
<ns1:HoursWorked>20</ns1:HoursWorked>
<ns1:Type>FullTimeHourly</ns1:Type>
</ns1:CurrentEmploymentRecord>
<ns1:CurrentIncome>
<ns1:Amount>5000</ns1:Amount>
<ns1:EffectiveDate>2014-01-01T00:00:00</ns1:EffectiveDate>
<ns1:Frequency>BiWeekly</ns1:Frequency>
<ns1:Type>Salary</ns1:Type>
</ns1:CurrentIncome>
<ns1:Dependents>
<ns1:CoveredLife>
<ns1:CoverageDeclines/>
<ns1:CoveredLifeHolder>
<ns1:Contacts/>
<ns1:DefaultAddress/>
<ns1:DefaultEmail/>
<ns1:DefaultPhone/>
<ns1:PreferredLanguage>ENG</ns1:PreferredLanguage>
<ns1:DateOfBirth>2009-05-09T00:00:00</ns1:DateOfBirth>
<ns1:FirstName>Sean Louis</ns1:FirstName>
<ns1:LastName>Carrier</ns1:LastName>
<ns1:***>Male</ns1:***>
</ns1:CoveredLifeHolder>
<ns1:DependentCategory>Child</ns1:DependentCategory>
<ns1:DependentSubCategory>Minor</ns1:DependentSubCategory>
<ns1:Number>03</ns1:Number>
</ns1:CoveredLife>
</ns1:Dependents>
<ns1:Division>
<ns1:Code>1</ns1:Code>
<ns1:EffectiveDate>2009-05-09T00:00:00</ns1:EffectiveDate>
</ns1:Division>
<ns1:FamilyCategory>Family</ns1:FamilyCategory>
<ns1:HealthCareSpendingAccountInformation/>
<ns1:HireDate>2002-07-15T00:00:00</ns1:HireDate>
<ns1:InsuredCoveredLife>
<ns1:CoverageDeclines/>
<ns1:CoveredLifeHolder>
<ns1:Contacts/>
<ns1:DefaultAddress ns2:type="ns1:CanadianAddress">
<ns1:City>Surrey</ns1:City>
<ns1:Country>CA</ns1:Country>
<ns1:Line1>98 - 10752 Guildford Drive</ns1:Line1>
<ns1:PostalCode>V3R 1W6</ns1:PostalCode>
<ns1:Province>BC</ns1:Province>
</ns1:DefaultAddress>
<ns1:DefaultEmail>
<ns1:CorrespondenceMethod>Email</ns1:CorrespondenceMethod>
<ns1:CorrespondenceType>Home</ns1:CorrespondenceType>
<ns1:Data>[email protected]</ns1:Data>
</ns1:DefaultEmail>
<ns1:DefaultPhone>
<ns1:CorrespondenceMethod>Telephone</ns1:CorrespondenceMethod>
<ns1:CorrespondenceType>Home</ns1:CorrespondenceType>
<ns1:Data>(001)(555)555-5555</ns1:Data>
</ns1:DefaultPhone>
<ns1:PreferredContact>Mail</ns1:PreferredContact>
<ns1:PreferredLanguage>ENG</ns1:PreferredLanguage>
<ns1:DateOfBirth>1974-02-07T00:00:00</ns1:DateOfBirth>
<ns1:FirstName>Krisztina</ns1:FirstName>
<ns1:LastName>Carrier</ns1:LastName>
<ns1:***>Female</ns1:***>
</ns1:CoveredLifeHolder>
<ns1:EffectiveDate>2007-06-01T00:00:00</ns1:EffectiveDate>
<ns1:Status>Inforce</ns1:Status>
</ns1:InsuredCoveredLife>
<ns1:JobTitle>Recreation Leader 2</ns1:JobTitle>
<ns1:Number>000050</ns1:Number>
<ns1:Plan>
<ns1:Code>9027380101</ns1:Code>
<ns1:EffectiveDate>2009-05-09T00:00:00</ns1:EffectiveDate>
</ns1:Plan>
<ns1:RegionalAdministration>
<ns1:Country>CA</ns1:Country>
<ns1:ProvinceOfBilling>BC</ns1:ProvinceOfBilling>
</ns1:RegionalAdministration>
<ns1:Section/>
</ns1:Certificate>
</ns1:Certificates>
</ns1:Policy>
Here is my XSL for removing empty nodes:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:strip-space elements="*"/>
    <xsl:template match="node()|@*">
        <xsl:copy>
            <xsl:apply-templates select="node()|@*"/>
        </xsl:copy>
    </xsl:template>
    <xsl:template match="*[not(@*) and not(*) and (not(text()) or .=-1)]"/>
</xsl:stylesheet>
This program removes all empty nodes except below nodes:
<ns1:Dependents>
<ns1:CoveredLife>
<ns1:CoverageDeclines/>
<ns1:CoveredLifeHolder>
<ns1:Contacts/>
<ns1:DefaultAddress/>
<ns1:DefaultEmail/>
<ns1:DefaultPhone/>
Please throw some ideas.
Thank you
John

Here is my XSD:
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:tns="http://pac.bluecross.ca/Common/Types" xmlns:ser="http://schemas.microsoft.com/2003/10/Serialization/" elementFormDefault="qualified" targetNamespace="http://pac.bluecross.ca/Common/Types" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:complexType name="BusinessObject">
    <xs:sequence>
    </xs:sequence>
</xs:complexType>
<xs:element name="BusinessObject" nillable="true" type="tns:BusinessObject" />
<xs:simpleType name="CancelReasonCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="LaidOff">
      </xs:enumeration>
      <xs:enumeration value="Retired">
      </xs:enumeration>
      <xs:enumeration value="Divorced">
      </xs:enumeration>
      <xs:enumeration value="Separated">
      </xs:enumeration>
      <xs:enumeration value="NoLongerEligibleForCoverage">
      </xs:enumeration>
      <xs:enumeration value="MaternityLeave">
      </xs:enumeration>
      <xs:enumeration value="LeaveOfAbsense">
      </xs:enumeration>
      <xs:enumeration value="OnDisability">
      </xs:enumeration>
      <xs:enumeration value="PensionExpired">
      </xs:enumeration>
      <xs:enumeration value="StrikeOrLockout">
      </xs:enumeration>
      <xs:enumeration value="TransferredToAnotherCarrier">
      </xs:enumeration>
      <xs:enumeration value="WaivedBenefitsNoReason">
      </xs:enumeration>
      <xs:enumeration value="WaivedBenefitsSpousalCoverage">
      </xs:enumeration>
      <xs:enumeration value="LeftCompany">
      </xs:enumeration>
      <xs:enumeration value="DisContinuedCoverage">
      </xs:enumeration>
      <xs:enumeration value="NoProvincialMedicalPlan">
      </xs:enumeration>
      <xs:enumeration value="Transferred">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="CancelReasonCodes" nillable="true" type="tns:CancelReasonCodes" />
<xs:simpleType name="CorrespondenceMethodCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Mail">
      </xs:enumeration>
      <xs:enumeration value="Telephone">
      </xs:enumeration>
      <xs:enumeration value="Email">
      </xs:enumeration>
      <xs:enumeration value="FTP">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="CorrespondenceMethodCodes" nillable="true" type="tns:CorrespondenceMethodCodes" />
<xs:simpleType name="CorrespondenceTypeCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Home">
      </xs:enumeration>
      <xs:enumeration value="Office">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="CorrespondenceTypeCodes" nillable="true" type="tns:CorrespondenceTypeCodes" />
<xs:simpleType name="CoveredLifeStatusCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Inforce">
      </xs:enumeration>
      <xs:enumeration value="Terminated">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="CoveredLifeStatusCodes" nillable="true" type="tns:CoveredLifeStatusCodes" />
<xs:simpleType name="DependentCategoryCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Child">
      </xs:enumeration>
      <xs:enumeration value="Spouse">
      </xs:enumeration>
      <xs:enumeration value="Insured">
      </xs:enumeration>
      <xs:enumeration value="Dependent">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="DependentCategoryCodes" nillable="true" type="tns:DependentCategoryCodes" />
<xs:simpleType name="DependentSubCategoryCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Student">
      </xs:enumeration>
      <xs:enumeration value="Minor">
      </xs:enumeration>
      <xs:enumeration value="CommonLaw">
      </xs:enumeration>
      <xs:enumeration value="Married">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="DependentSubCategoryCodes" nillable="true" type="tns:DependentSubCategoryCodes" />
<xs:simpleType name="EmploymentTypeCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Director">
      </xs:enumeration>
      <xs:enumeration value="FullTimeSalary">
      </xs:enumeration>
      <xs:enumeration value="FullTimeHourly">
      </xs:enumeration>
      <xs:enumeration value="PartTimeSalary">
      </xs:enumeration>
      <xs:enumeration value="PartTimeHourly">
      </xs:enumeration>
      <xs:enumeration value="OwnerOperator">
      </xs:enumeration>
      <xs:enumeration value="Retired">
      </xs:enumeration>
      <xs:enumeration value="Seasonal">
      </xs:enumeration>
      <xs:enumeration value="Casual">
      </xs:enumeration>
      <xs:enumeration value="Client">
      </xs:enumeration>
      <xs:enumeration value="Consultant">
      </xs:enumeration>
      <xs:enumeration value="Contract">
      </xs:enumeration>
      <xs:enumeration value="ElectedOfficial">
      </xs:enumeration>
      <xs:enumeration value="JobShare">
      </xs:enumeration>
      <xs:enumeration value="Temporary">
      </xs:enumeration>
      <xs:enumeration value="Volunteer">
      </xs:enumeration>
      <xs:enumeration value="MSDRecipientnotEE">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="EmploymentTypeCodes" nillable="true" type="tns:EmploymentTypeCodes" />
<xs:simpleType name="FamilyCategoryCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Single">
      </xs:enumeration>
      <xs:enumeration value="Family">
      </xs:enumeration>
      <xs:enumeration value="Couple">
      </xs:enumeration>
      <xs:enumeration value="NotApplicable">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="FamilyCategoryCodes" nillable="true" type="tns:FamilyCategoryCodes" />
<xs:simpleType name="FrequencyCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Annual">
      </xs:enumeration>
      <xs:enumeration value="BiMonthly">
      </xs:enumeration>
      <xs:enumeration value="BiWeekly">
      </xs:enumeration>
      <xs:enumeration value="Hourly">
      </xs:enumeration>
      <xs:enumeration value="Monthly">
      </xs:enumeration>
      <xs:enumeration value="Quarterly">
      </xs:enumeration>
      <xs:enumeration value="SemiAnnually">
      </xs:enumeration>
      <xs:enumeration value="SemiMonthly">
      </xs:enumeration>
      <xs:enumeration value="Weekly">
      </xs:enumeration>
      <xs:enumeration value="LifeTime">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="FrequencyCodes" nillable="true" type="tns:FrequencyCodes" />
<xs:simpleType name="IncomeTypeCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Salary">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="IncomeTypeCodes" nillable="true" type="tns:IncomeTypeCodes" />
<xs:simpleType name="LanguageCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="ENG">
      </xs:enumeration>
      <xs:enumeration value="FRA">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="LanguageCodes" nillable="true" type="tns:LanguageCodes" />
<xs:simpleType name="LineOfBusinessCategoryCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Health">
      </xs:enumeration>
      <xs:enumeration value="Dental">
      </xs:enumeration>
      <xs:enumeration value="Life">
      </xs:enumeration>
      <xs:enumeration value="AccidentalDeathAndDismemberment">
      </xs:enumeration>
      <xs:enumeration value="Disability">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="LineOfBusinessCategoryCodes" nillable="true" type="tns:LineOfBusinessCategoryCodes" />
<xs:simpleType name="ProvinceCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="AB">
      </xs:enumeration>
      <xs:enumeration value="BC">
      </xs:enumeration>
      <xs:enumeration value="MB">
      </xs:enumeration>
      <xs:enumeration value="NB">
      </xs:enumeration>
      <xs:enumeration value="NL">
      </xs:enumeration>
      <xs:enumeration value="NT">
      </xs:enumeration>
      <xs:enumeration value="NS">
      </xs:enumeration>
      <xs:enumeration value="ON">
      </xs:enumeration>
      <xs:enumeration value="PE">
      </xs:enumeration>
      <xs:enumeration value="QC">
      </xs:enumeration>
      <xs:enumeration value="SK">
      </xs:enumeration>
      <xs:enumeration value="YT">
      </xs:enumeration>
      <xs:enumeration value="NU">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="ProvinceCodes" nillable="true" type="tns:ProvinceCodes" />
<xs:simpleType name="ReapplicationReasonCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Exception">
      </xs:enumeration>
      <xs:enumeration value="Invalid">
      </xs:enumeration>
      <xs:enumeration value="Valid">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="ReapplicationReasonCodes" nillable="true" type="tns:ReapplicationReasonCodes" />
<xs:simpleType name="SexCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Male">
      </xs:enumeration>
      <xs:enumeration value="Female">
      </xs:enumeration>
      <xs:enumeration value="NotApplicable">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="SexCodes" nillable="true" type="tns:SexCodes" />
<xs:simpleType name="StateCodes">
    <xs:restriction base="xs:string">
      <xs:enumeration value="AL">
      </xs:enumeration>
      <xs:enumeration value="AK">
      </xs:enumeration>
      <xs:enumeration value="AZ">
      </xs:enumeration>
      <xs:enumeration value="AR">
      </xs:enumeration>
      <xs:enumeration value="CA">
      </xs:enumeration>
      <xs:enumeration value="Colorado">
      </xs:enumeration>
      <xs:enumeration value="CT">
      </xs:enumeration>
      <xs:enumeration value="DE">
      </xs:enumeration>
      <xs:enumeration value="DC">
      </xs:enumeration>
      <xs:enumeration value="FL">
      </xs:enumeration>
      <xs:enumeration value="GA">
      </xs:enumeration>
      <xs:enumeration value="HI">
      </xs:enumeration>
      <xs:enumeration value="ID">
      </xs:enumeration>
      <xs:enumeration value="IL">
      </xs:enumeration>
      <xs:enumeration value="IN">
      </xs:enumeration>
      <xs:enumeration value="IA">
      </xs:enumeration>
      <xs:enumeration value="KS">
      </xs:enumeration>
      <xs:enumeration value="KY">
      </xs:enumeration>
      <xs:enumeration value="LA">
      </xs:enumeration>
      <xs:enumeration value="ME">
      </xs:enumeration>
      <xs:enumeration value="MD">
      </xs:enumeration>
      <xs:enumeration value="MA">
      </xs:enumeration>
      <xs:enumeration value="MI">
      </xs:enumeration>
      <xs:enumeration value="MN">
      </xs:enumeration>
      <xs:enumeration value="MS">
      </xs:enumeration>
      <xs:enumeration value="MO">
      </xs:enumeration>
      <xs:enumeration value="MT">
      </xs:enumeration>
      <xs:enumeration value="NE">
      </xs:enumeration>
      <xs:enumeration value="NV">
      </xs:enumeration>
      <xs:enumeration value="NH">
      </xs:enumeration>
      <xs:enumeration value="NJ">
      </xs:enumeration>
      <xs:enumeration value="NM">
      </xs:enumeration>
      <xs:enumeration value="NY">
      </xs:enumeration>
      <xs:enumeration value="NC">
      </xs:enumeration>
      <xs:enumeration value="ND">
      </xs:enumeration>
      <xs:enumeration value="OH">
      </xs:enumeration>
      <xs:enumeration value="OK">
      </xs:enumeration>
      <xs:enumeration value="OR">
      </xs:enumeration>
      <xs:enumeration value="PA">
      </xs:enumeration>
      <xs:enumeration value="RI">
      </xs:enumeration>
      <xs:enumeration value="SC">
      </xs:enumeration>
      <xs:enumeration value="SD">
      </xs:enumeration>
      <xs:enumeration value="TN">
      </xs:enumeration>
      <xs:enumeration value="TX">
      </xs:enumeration>
      <xs:enumeration value="UT">
      </xs:enumeration>
      <xs:enumeration value="VT">
      </xs:enumeration>
      <xs:enumeration value="VA">
      </xs:enumeration>
      <xs:enumeration value="WA">
      </xs:enumeration>
      <xs:enumeration value="WV">
      </xs:enumeration>
      <xs:enumeration value="WI">
      </xs:enumeration>
      <xs:enumeration value="WY">
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
<xs:element name="StateCodes" nillable="true" type="tns:StateCodes" />
<xs:complexType name="Address">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="City" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Country" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Line1" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Line2" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Line3" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Line4" nillable="true" type="xs:string">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Address" nillable="true" type="tns:Address" />
<xs:complexType name="InternationalAddress">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Address">
        <xs:sequence>
          <xs:element minOccurs="0" name="Region" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="PostalCode" nillable="true" type="xs:string">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="InternationalAddress" nillable="true" type="tns:InternationalAddress" />
<xs:complexType name="CanadianAddress">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Address">
        <xs:sequence>
          <xs:element minOccurs="0" name="PostalCode" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Province" nillable="true" type="tns:ProvinceCodes" />
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="CanadianAddress" nillable="true" type="tns:CanadianAddress" />
<xs:complexType name="AmericanAddress">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Address">
        <xs:sequence>
          <xs:element minOccurs="0" name="State" nillable="true" type="tns:StateCodes">
          </xs:element>
          <xs:element minOccurs="0" name="ZipCode" nillable="true" type="xs:string">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="AmericanAddress" nillable="true" type="tns:AmericanAddress" />
<xs:complexType name="Person">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Client">
        <xs:sequence>
          <xs:element minOccurs="0" name="DateOfBirth" nillable="true" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="FirstName" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="LastName" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="MaidenName" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="MiddleName" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="PreferredName" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="***" type="tns:SexCodes">
          </xs:element>
          <xs:element minOccurs="0" name="Suffix" nillable="true" type="xs:string">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Person" nillable="true" type="tns:Person" />
<xs:complexType name="Client">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="Contacts" nillable="true" type="tns:ArrayOfContactInformation">
          </xs:element>
          <xs:element minOccurs="0" name="DefaultAddress" nillable="true" type="tns:Address">
          </xs:element>
          <xs:element minOccurs="0" name="DefaultEmail" nillable="true" type="tns:ContactInformation">
          </xs:element>
          <xs:element minOccurs="0" name="DefaultPhone" nillable="true" type="tns:ContactInformation">
          </xs:element>
          <xs:element minOccurs="0" name="PreferredContact" nillable="true" type="tns:CorrespondenceMethodCodes">
          </xs:element>
          <xs:element minOccurs="0" name="PreferredLanguage" nillable="true" type="tns:LanguageCodes">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Client" nillable="true" type="tns:Client" />
<xs:complexType name="Division">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Structurable">
        <xs:sequence>
          <xs:element minOccurs="0" name="Code" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="SubDivisions" nillable="true" type="tns:ArrayOfDivision">
          </xs:element>
          <xs:element minOccurs="0" name="EffectiveDate" nillable="true" type="xs:dateTime">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Division" nillable="true" type="tns:Division" />
<xs:complexType name="Structurable">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Structurable" nillable="true" type="tns:Structurable" />
<xs:complexType name="CoveredLife">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="ApplicationDate" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="CancelReason" nillable="true" type="tns:CancelReasonCodes">
          </xs:element>
          <xs:element minOccurs="0" name="CoverageDeclines" nillable="true" type="tns:ArrayOfBenefitDecline">
          </xs:element>
          <xs:element minOccurs="0" name="CoveredLifeHolder" nillable="true" type="tns:Person">
          </xs:element>
          <xs:element minOccurs="0" name="DependentCategory" nillable="true" type="tns:DependentCategoryCodes">
          </xs:element>
          <xs:element minOccurs="0" name="DependentSubCategory" nillable="true" type="tns:DependentSubCategoryCodes">
          </xs:element>
          <xs:element minOccurs="0" name="EffectiveDate" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="Number" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="QualificationDate" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="Status" nillable="true" type="tns:CoveredLifeStatusCodes">
          </xs:element>
          <xs:element minOccurs="0" name="TerminationDate" type="xs:dateTime">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="CoveredLife" nillable="true" type="tns:CoveredLife" />
<xs:complexType name="Certificate">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="Class" nillable="true" type="tns:Class">
          </xs:element>
          <xs:element minOccurs="0" name="CurrentEmploymentRecord" nillable="true" type="tns:EmploymentRecord">
          </xs:element>
          <xs:element minOccurs="0" name="CurrentIncome" nillable="true" type="tns:Income">
          </xs:element>
          <xs:element minOccurs="0" name="Dependents" nillable="true" type="tns:ArrayOfCoveredLife">
          </xs:element>
          <xs:element minOccurs="0" name="Division" nillable="true" type="tns:Division">
          </xs:element>
          <xs:element minOccurs="0" name="FamilyCategory" nillable="true" type="tns:FamilyCategoryCodes">
          </xs:element>
          <xs:element minOccurs="0" name="HealthCareSpendingAccountInformation" nillable="true" type="tns:HealthCareSpendingAccountInformation">
          </xs:element>
          <xs:element minOccurs="0" name="HireDate" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="InsuredCoveredLife" nillable="true" type="tns:CoveredLife">
          </xs:element>
          <xs:element minOccurs="0" name="JobTitle" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Number" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="PayrollNumber" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Plan" nillable="true" type="tns:Plan">
          </xs:element>
          <xs:element minOccurs="0" name="RegionalAdministration" nillable="true" type="tns:RegionalAdministrativeInformation">
          </xs:element>
          <xs:element minOccurs="0" name="Section" nillable="true" type="tns:Section">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Certificate" nillable="true" type="tns:Certificate" />
<xs:complexType name="Policy">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Structurable">
        <xs:sequence>
          <xs:element minOccurs="0" name="Code" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="Certificates" nillable="true" type="tns:ArrayOfCertificate">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Policy" nillable="true" type="tns:Policy" />
<xs:complexType name="Class">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Structurable">
        <xs:sequence>
          <xs:element minOccurs="0" name="Code" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="EffectiveDate" type="xs:dateTime">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Class" nillable="true" type="tns:Class" />
<xs:complexType name="Plan">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:Structurable">
        <xs:sequence>
          <xs:element minOccurs="0" name="Code" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="EffectiveDate" type="xs:dateTime" />
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Plan" nillable="true" type="tns:Plan" />
<xs:complexType name="ArrayOfPolicy">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="Policy" nillable="true" type="tns:Policy" />
    </xs:sequence>
</xs:complexType>
<xs:element name="ArrayOfPolicy" nillable="true" type="tns:ArrayOfPolicy" />
<xs:complexType name="BenefitDecline">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="ChangeEffectiveDate" nillable="true" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="DeclineReason" nillable="true" type="tns:CancelReasonCodes">
          </xs:element>
          <xs:element minOccurs="0" name="Declined" nillable="true" type="xs:boolean">
          </xs:element>
          <xs:element minOccurs="0" name="LineOfBusinessCategory" nillable="true" type="tns:LineOfBusinessCategoryCodes">
          </xs:element>
          <xs:element minOccurs="0" name="ReapplicationReason" nillable="true" type="tns:ReapplicationReasonCodes">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="BenefitDecline" nillable="true" type="tns:BenefitDecline" />
<xs:complexType name="ContactInformation">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="CorrespondenceMethod" nillable="true" type="tns:CorrespondenceMethodCodes">
          </xs:element>
          <xs:element minOccurs="0" name="CorrespondenceNote" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="CorrespondenceType" nillable="true" type="tns:CorrespondenceTypeCodes">
          </xs:element>
          <xs:element minOccurs="0" name="Data" nillable="true" type="xs:string">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="ContactInformation" nillable="true" type="tns:ContactInformation" />
<xs:complexType name="EmploymentRecord">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="EffectiveDate" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="Frequency" nillable="true" type="tns:FrequencyCodes">
          </xs:element>
          <xs:element minOccurs="0" name="HoursWorked" type="xs:decimal">
          </xs:element>
          <xs:element minOccurs="0" name="SalaryAmount" nillable="true" type="xs:decimal">
          </xs:element>
          <xs:element minOccurs="0" name="Type" nillable="true" type="tns:EmploymentTypeCodes">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="EmploymentRecord" nillable="true" type="tns:EmploymentRecord" />
<xs:complexType name="Enrollment">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="Policies" nillable="true" type="tns:ArrayOfPolicy">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Enrollment" nillable="true" type="tns:Enrollment" />
<xs:complexType name="HealthCareSpendingAccountInformation">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="AllocationAmount" type="xs:decimal">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="HealthCareSpendingAccountInformation" nillable="true" type="tns:HealthCareSpendingAccountInformation" />
<xs:complexType name="Income">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="Amount" type="xs:decimal">
          </xs:element>
          <xs:element minOccurs="0" name="EffectiveDate" type="xs:dateTime">
          </xs:element>
          <xs:element minOccurs="0" name="Frequency" nillable="true" type="tns:FrequencyCodes">
          </xs:element>
          <xs:element minOccurs="0" name="Type" nillable="true" type="tns:IncomeTypeCodes">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Income" nillable="true" type="tns:Income" />
<xs:complexType name="RegionalAdministrativeInformation">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="Country" nillable="true" type="xs:string">
          </xs:element>
          <xs:element minOccurs="0" name="ProvinceOfBilling" nillable="true" type="tns:ProvinceCodes">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="RegionalAdministrativeInformation" nillable="true" type="tns:RegionalAdministrativeInformation" />
<xs:complexType name="Section">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:BusinessObject">
        <xs:sequence>
          <xs:element minOccurs="0" name="Code" nillable="true" type="xs:string">
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:element name="Section" nillable="true" type="tns:Section" />
<xs:complexType name="ArrayOfContactInformation">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="ContactInformation" nillable="true" type="tns:ContactInformation" />
    </xs:sequence>
</xs:complexType>
<xs:element name="ArrayOfContactInformation" nillable="true" type="tns:ArrayOfContactInformation" />
<xs:complexType name="ArrayOfDivision">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="Division" nillable="true" type="tns:Division" />
    </xs:sequence>
</xs:complexType>
<xs:element name="ArrayOfDivision" nillable="true" type="tns:ArrayOfDivision" />
<xs:complexType name="ArrayOfCertificate">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="Certificate" nillable="true" type="tns:Certificate" />
    </xs:sequence>
</xs:complexType>
<xs:element name="ArrayOfCertificate" nillable="true" type="tns:ArrayOfCertificate" />
<xs:complexType name="ArrayOfCoveredLife">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="CoveredLife" nillable="true" type="tns:CoveredLife" />
    </xs:sequence>
</xs:complexType>
<xs:element name="ArrayOfCoveredLife" nillable="true" type="tns:ArrayOfCoveredLife" />
<xs:complexType name="ArrayOfBenefitDecline">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="BenefitDecline" nillable="true" type="tns:BenefitDecline" />
    </xs:sequence>
</xs:complexType>
<xs:element name="ArrayOfBenefitDecline" nillable="true" type="tns:ArrayOfBenefitDecline" />
</xs:schema>

Removing empty node created by Value Mapping Functoid

If the first input parameter to Value Mapping functoid is not true, it creates an empty element in the destination which I don't want, how can I get rid of this empty element, if it's empty I do not want it to created in the destination document.
Do let me know how can I achive this within a Map.

You can get rid of the empty nodes in your map by using a custom functoid and use XSLT script (also given below) and mentioned in this article
Remove empty nodes in BizTalk by using XSLT
<?xml version="1.0" ?>
<xsl:stylesheet xmlns:xsl="@@ YOUR NAMESPACE @@" version="1.0" xmlns:ns0="http://Stater.Isvcs.Iface.BO.GetLoanData.ElfV2">
    <xsl:output method="xml" indent="yes" />
    <xsl:template match="node()">
        <xsl:if test="count(descendant::text()[string-length(normalize-space(.))>0]|@*)">
            <xsl:copy>
                <xsl:apply-templates select="@*|node()" />
            </xsl:copy>
        </xsl:if>
    </xsl:template>
    <xsl:template match="@*">
        <xsl:copy />
    </xsl:template>
    <xsl:template match="text()">
        <xsl:value-of select="normalize-space(.)" />
    </xsl:template>
</xsl:stylesheet>
Abdul Rafay - MVP & MCTS BizTalk Server
blog: http://abdulrafaysbiztalk.wordpress.com/
Please mark this as answer if it helps.

How do you remove duplicate note events 1 or to ticks apart ?

How do you remove duplicate note events 1 or to ticks apart ?
my keyboard was putting out doubled note events durring a session.
But the note events are between 1 and 3 cliks apart.
in other words 1 might be at 1 3 151 and the other duplicate at 1 3 153
So remove duplicate events does not work.
I dont want to have to quatize all events either.
thanks
CC
Logic X

The only other option I can think of that may help you is the select highest/lowest notes.
This will select the top or bottom notes for any notes that are overlapping.
the key command is :
**** up ( highest ) or shift down ( lowest )
It may work on some blocks of notes, but it's a bit hit and miss.
Other than that it's a manual editing job I'm afraid

Remove empty object frame

How to remove empty object frame.(rectangle without image)

I try the below code but it delete tables inside rectangle. i tried in javascript.
var doc = app.activeDocument;
var myPages = app.activeDocument.pages;
    for (var p = 0; p < myPages.length; p++)
                         var myGraphicFrames = app.activeDocument.pages[p].rectangles;
                         for (j = myGraphicFrames.length - 1; j >= 0; j--)
                                   if (myGraphicFrames[j].graphics.length == 0)
                                             app.selection = myGraphicFrames[j];
                                             alert (app.activeWindow.activePage.name);

Remove empty folders revisited

Hi,
A while back I did start using this to remove empty folders inside a download folder ( thanks tot Bob for the time delay )
/usr/bin/find $dlDir -depth -empty -type d -Bmin +2880 -exec rmdir {} ;
Now, I need to remove folders inside many projects folder, but this isn't working for folders where a .DS_Store file lives inside.
I could loop in each folder to check for a 1 file count ( or for more .xxx files ), but this will take time.
How can I do that in a faster way?
I dont want to remove any .DS_Store file from a folder that isn't empty with other files.
Thanks in advance
( I know how to do it in applescript, but, I need/want it in bash )

So I could replace eventually
echo rm -f "$dir/.DS_Store" # remove the 'echo' when you think it is safe
echo rmdir "$dir"
with I guess.
echo rm -rf "$dir" # remove the 'echo' when you think it is safe
But will try that, the above, later.
I thought about using rm -rf, but I worry about accidentally getting a wrong path, and deleting too much. Years ago, I wrote a script (similar concept to what you are trying to do), that was suppose to clean up a scratch area. I made a mistake in my script and cleaned out /etc/. The system was essentially hosed and I had to restore from backups.
While I do use rm -rf, I am very careful about when I use it. It is also why I just 'echo'ed out the rm commands, rather than execute them during testing.
If I have the wrong directory somehow, rm -f .DS_Store and rmdir "$dir" will do the minimum amount of damage, as the rmdir will not delete a directory unless it is empty, so my only loss would be the .DS_Store.
Also I could replace
'! -iname .DS_Store' with '! -iname ".*"' for searching and keeping out of the $files var any 'just hidden files' in the folder, right?
Yes that should work, but I think you want to understand what dot files are there any why.
as each directory found will be searched for files besides .DS_Store, but I could not figure out a way to do this all within the single 'find' command that was not messy.
This was my fear, so I ask the pro's! , but I see there is not a real choice without looping.
There may be a way, I just could not think of a cool trick that would do it.

Remove "Empty Demarcation"

How can I remove "Empty Demarcation" in the Text Elements. When I don't pass value(optional variable) to web template it shows "Empty Demarcation" in the report text elements, I want to convert into blank or "ALL".
Should be grateful for any futher information
regards
supriatna

Hi Heike,
I had change text 301 become "All" and make SAPLRRSV active but "empty demarcation" is still show in the web,
any other suggestion.
I think the system not directly changes the text in the web after 2 day the changes run correctly,
btw thanks Heike for your post.
thanks
supriatna
Message was edited by: BW - xltrs

ICal calendar list empty but events still visible

So here's the problem. I open iCal last night, and my calendar list is empty. Also, when I open iCal there are no events visible until I change views (say from week to month or month to day). The same is true of my tasks. Even after changing views, though, my calendar list is still empty. The only change I've made in the last day or two is to have iCal sync my calendars with .Mac.
I'm running 10.4.3 on a 17 inch Powerbook G4 1GHz with 1GB RAM. I'd appreciate any help. Thanks.

ellisjs,
I'm having the same problems that you describe. There is another thread in the forums that discuss the same issues. One user, Norm, Gilbert, offers a solution that has worked for him.
"If I remember the steps, they involved removing the following items in the user library:
~\library\preferences\com.apple.iCal.AlarmScheduler.plist
~\library\preferences\com.apple.iCal.helper.plist
~\library\preferences\com.apple.iCal.plist
and then deleting the .plist files from here:
~\library\application suport\iCal
and then moving the Sources folder from here to the Desktop:
~\library\application suport\iCal
Then a restarted my Mac and lunched iCal. Everything worked as expected and has continued to work properly even after adding events, re-starting and doing a sync with Mark Space Missing Sync.
Knock on wood, it keeps working."
After following his steps it works until I launch iCal again. It varies from now showing my calendars to not showing my To Do's. I have not seen any fixes that work yet, but will continue to monitor this thread for any solutions. It appears to be a 10.4.3 issue from I have seen so far.

Removing empty photostream events

Similar Messages

Maybe you are looking for