Format numeric field--am losing slicer context

[ThomasDay]

Hello all,

I'm stumped.  I've gone around and around on formatting a tel. number field and am seeing some really unpredictable context changes.  I create a measure...it is a text data type.

HospicePhone = 
 VAR PhoneNumber = LOOKUPVALUE(HospiceProfiles[Telephone Number], HospiceProfiles[CCN], 
 FIRSTNONBLANK(MergedProviders[CCN],MergedProviders[CCN]))
 RETURN 
 PhoneNumber

The results in a table look fine and so now I want to format the text version of the phone.  Notice that all the entries are in AR, set by a slicer.  So now it's time to format it...

HospicePhone = 
 VAR PhoneNumber = LOOKUPVALUE(HospiceProfiles[Telephone Number], HospiceProfiles[CCN], 
 FIRSTNONBLANK(MergedProviders[CCN],MergedProviders[CCN]))
 VAR PhoneToFormat = FORMAT(VALUE(PhoneNumber),"\(000\)000\-0000")
 RETURN 
 PhoneToFormat

So I've tried a zillion versions of things to format:  Here's one and it fails.  Notice how the table NOW includes FL...And the phone is blank for all but the slicer state of AR.  I can filter the visual to eliminate blanks...all looks fine, but what the heck is going on?  Not to mention, if a provider doesn't have a phone number, the filter will eliminate that row...so it's not ideal.  

 Why does adding a format change the slicer context?  Hope this is clear enough to figure out what I'm asking and thanks in advance, Tom

[v-yuezhe-msft]

@ThomasDay,

I am not able to reproduce your issue when using the above formula to format the measure in my sample table, could you please share me the data in your MergedProviders table and HospiceProfiles table so that I can test?



Regards,