Error when saving properties even if filled out

%3CLINGO-SUB%20id%3D%22lingo-sub-393670%22%20slang%3D%22en-US%22%3EError%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393670%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20discovered%20something%20that%20might%20be%20a%20bug.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20document%20library%20with%20some%20custom%20columns.%20One%20column%20is%20of%20type%20Managed%20Metadata%2C%20and%20set%20to%20be%20Required.%20Column%20name%20is%20External%20Company.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20uploading%20the%20document%2C%20I%20open%20the%20Details%20pane%2C%20and%20enter%20a%20valid%20label%20into%20External%20Company.%20Then%20change%20focus%20to%20another%20column%2C%20and%20can%20verify%20that%20the%20new%20value%20is%20saved.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20if%20I%20do%20the%20same%20using%20the%20%22Edit%20all%22%20option%2C%20I%20get%20an%20error%20message%20saying%20%22You%20can't%20leave%20this%20blank%22%20when%20hitting%20the%20Save%20button.%20See%20screenshot%20below%3A%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20905px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F101580i7D4989A5FD731554%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22image.png%22%20title%3D%22image.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20confirm%20that%20the%20value%20in%20the%20screenshot%20above%20is%20indeed%20a%20valid%20term%20in%20the%20Term%20Store%2C%20and%20that%20this%20error%20applies%20to%20other%20terms%20from%20the%20Term%20Store%20as%20well.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20experienced%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20any%20input%20or%20insight!%3C%2FP%3E%3CP%3EKind%20Regards%2C%26nbsp%3B%3C%2FP%3E%3CP%3EFrank%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-393670%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-456530%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-456530%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F894%22%20target%3D%22_blank%22%3E%40Frank-Ove%20Kristiansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHey%20Frank-%20I%20have%20a%20user%20experiencing%20the%20same%20issue.%26nbsp%3B%20When%20I%20access%20the%20document%20properties%20I%20have%20no%20problems%20updating%20the%20fields.%26nbsp%3B%20I%20watched%20the%20user%20input%20as%20well%20so%20I%20know%20it%20is%20not%20a%20user%20error.%26nbsp%3B%20I%20recommended%20a%20restart%20and%20clearing%20browser%20data%20to%20see%20if%20that%20helps%20*crosses%20fingers*.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20I%20have%20not%20found%20any%20other%20info%20on%20this%20one%3B%20you%20are%20not%20alone%20however!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-Thomas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-467031%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-467031%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F894%22%20target%3D%22_blank%22%3E%40Frank-Ove%20Kristiansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20experiencing%20the%20same%20issue.%20Hoping%20that%20someone%20with%20a%20solution%20replies%20soon.%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%2C%20I%20don't%20have%20the%20answer%2C%20but%20you%20are%20definitely%20not%20alone.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482265%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482265%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F894%22%20target%3D%22_blank%22%3E%40Frank-Ove%20Kristiansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20came%20in%20here%20looking%20for%20a%20similar%20problem%20that%20I%20think%20is%20related.%26nbsp%3B%20In%20my%20case%20I%20have%20a%20simple%20modern%20list%20with%20a%20column%20in%20it%20to%20hold%20numbers.%26nbsp%3B%20I%20can%20go%20into%20that%20item%2C%20and%20change%20a%202%20to%20a%203%2C%20and%20watch%20the%20darn%20thing%20change%20back%20to%20a%202%20again%20right%20as%20it%20waves%20a%20little%20%22saved%22%20at%20me%20when%20I%20take%20my%20focus%20away%20to%20another%20field.%26nbsp%3B%20But%20if%20I%20go%20land%20back%20in%20the%20field%20a%20second%20time%2C%20the%203%20will%20pop%20up%20again%20the%20way%20I%20want%20it%20to%20be%2C%20and%20it%20may%20or%20may%20not%20tell%20me%20for%20a%20second%20time%20that%20it%20has%20saved%2C%20but%20the%203%20will%20stick.%26nbsp%3B%20If%20I%20don't%20actually%20go%20back%20in%20to%20check%20the%20field%2C%20that%203%20will%20still%20have%20stuck%20anyway%2C%20but%20I'm%20paranoid%20and%20want%20to%20make%20sure%20it's%20there.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20would%20agree%20there's%20definitely%20something%20buggy%20going%20on%20with%20the%20Edit%20Item%20dialogue%20box%20as%20it%20relates%20to%20editing%20fields%20of%20data%20and%20the%20save-on-the-fly%20process.%26nbsp%3B%20I've%20tested%20with%20a%20couple%20of%20Win10%20machines%20both%20IE11%20and%20Chrome%2C%20all%20same%20buggy%20behavior.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20suggestion%20for%20your%20scenario%20where%20it's%20saying%20can't%20be%20blank%20...%20try%20landing%20back%20into%20the%20field%20again%20for%20that%20second%20helping%20of%20field-level%20%22save%22%20and%20see%20if%20that%20helps.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482280%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482280%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F894%22%20target%3D%22_blank%22%3E%40Frank-Ove%20Kristiansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%20I%20do%20not%20have%20the%20answer%20but%20I%20have%20the%20same%20issue%20for%20a%20client.%20We%20had%20to%20remove%20the%20column%20required%20(*)%20property%20for%20the%20managed%20metadata%20columns%20to%20be%20able%20to%20save.%20We%20still%20looking%20for%20a%20solution.%20Thank%20you!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-498250%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-498250%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F894%22%20target%3D%22_blank%22%3E%40Frank-Ove%20Kristiansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%20this%20definitely%20is%20an%20issue%20-%20but%20there%20is%20a%20workaround.%3C%2FP%3E%3CP%3EIf%20you%20click%20on%20the%20'tag'%20icons%20to%20select%20a%20value%20for%20your%20managed%20metadata%20column%20(from%20the%20resulting%20pop-up%20menu)%2C%20then%20you%20will%20experience%20this%20issue%20where%20you%20cannot%20save%20the%20item%20as%20the%20column%20is%20required.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWorkaround%3A%26nbsp%3B%3C%2FSTRONG%3EInstead%20of%20clicking%20on%20the%20'tag'%20icon%2C%20if%20you%20just%20just%20start%20typing%20in%20the%20value%20of%20the%20metadata%20column%20that%20you%20require%2C%20it%20will%20auto-complete%20-%20from%20which%20you%20can%20select%20the%20value%20you%20want.%20That%20method%20works%20fine%20without%20it%20incorrectly%20stating%20'You%20can't%20leave%20this%20blank'.%26nbsp%3BYou%20can%20now%20save%20your%20item.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-499915%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-499915%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F894%22%20target%3D%22_blank%22%3E%40Frank-Ove%20Kristiansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20issue%20here%20with%20a%20customer.%20We%20figured%20out%2C%20that%20this%20seems%20to%20be%20related%20to%20the%20%22Modern%20Experience%22%20-%20changing%20back%20to%20%22classic%22%20and%20we%20can%20fill%20the%20form%20without%20a%20problem%20or%20any%20strange%20error-messages.%3C%2FP%3E%3CP%3EHope%20someone%20will%20find%20a%20solution%20for%20that%20-%20makes%20no%20sense%20to%20switch%20to%20classic%20view%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-507601%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-507601%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F894%22%20target%3D%22_blank%22%3E%40Frank-Ove%20Kristiansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20checked%20today%20(1st%20May%202019)%20and%20this%20issue%20seems%20to%20have%20been%20resolved.%20Is%20everyone%20else%20finding%20this%20is%20the%20case%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAJ%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-510875%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-510875%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309158%22%20target%3D%22_blank%22%3E%40ashokjingar%3C%2FA%3E%2C%3C%2FP%3E%3CP%3EI%20tried%20recreating%20the%20issue%20today%2C%20but%20was%20unable%20to.%20So%20it%20might%20seem%20that%20this%20has%20been%20fixed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-525049%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-525049%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309158%22%20target%3D%22_blank%22%3E%40ashokjingar%3C%2FA%3E%26nbsp%3Bi%20can%20also%20confirm%20that%20the%20issue%20no%20longer%20persists%20for%20my%20customer.%20Great%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1434668%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1434668%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F329796%22%20target%3D%22_blank%22%3E%40Dominik_N%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20this%20still%20appears%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1436379%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20saving%20properties%20even%20if%20filled%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1436379%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309158%22%20target%3D%22_blank%22%3E%40ashokjingar%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYES%20i%20do.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Senior Member

Hi all,

 

I just discovered something that might be a bug.

 

I have a document library with some custom columns. One column is of type Managed Metadata, and set to be Required. Column name is External Company.

 

After uploading the document, I open the Details pane, and enter a valid label into External Company. Then change focus to another column, and can verify that the new value is saved. 

 

However, if I do the same using the "Edit all" option, I get an error message saying "You can't leave this blank" when hitting the Save button. See screenshot below:image.png

 

I can confirm that the value in the screenshot above is indeed a valid term in the Term Store, and that this error applies to other terms from the Term Store as well. 

 

Has anyone else experienced this?

 

Thanks for any input or insight!

Kind Regards, 

Frank

22 Replies

@Frank-Ove Kristiansen 

 

Hey Frank- I have a user experiencing the same issue.  When I access the document properties I have no problems updating the fields.  I watched the user input as well so I know it is not a user error.  I recommended a restart and clearing browser data to see if that helps *crosses fingers*.

 

Unfortunately I have not found any other info on this one; you are not alone however!

 

-Thomas

@Frank-Ove Kristiansen 

 

I am experiencing the same issue. Hoping that someone with a solution replies soon. :) 

 

Sorry, I don't have the answer, but you are definitely not alone.

@Frank-Ove Kristiansen 

 

I came in here looking for a similar problem that I think is related.  In my case I have a simple modern list with a column in it to hold numbers.  I can go into that item, and change a 2 to a 3, and watch the darn thing change back to a 2 again right as it waves a little "saved" at me when I take my focus away to another field.  But if I go land back in the field a second time, the 3 will pop up again the way I want it to be, and it may or may not tell me for a second time that it has saved, but the 3 will stick.  If I don't actually go back in to check the field, that 3 will still have stuck anyway, but I'm paranoid and want to make sure it's there.  

 

So I would agree there's definitely something buggy going on with the Edit Item dialogue box as it relates to editing fields of data and the save-on-the-fly process.  I've tested with a couple of Win10 machines both IE11 and Chrome, all same buggy behavior.

 

A suggestion for your scenario where it's saying can't be blank ... try landing back into the field again for that second helping of field-level "save" and see if that helps. 

@Frank-Ove Kristiansen 

 

Hi, I do not have the answer but I have the same issue for a client. We had to remove the column required (*) property for the managed metadata columns to be able to save. We still looking for a solution. Thank you! 

@Frank-Ove Kristiansen 

 

Hi, this definitely is an issue - but there is a workaround.

If you click on the 'tag' icons to select a value for your managed metadata column (from the resulting pop-up menu), then you will experience this issue where you cannot save the item as the column is required. 

Workaround: Instead of clicking on the 'tag' icon, if you just just start typing in the value of the metadata column that you require, it will auto-complete - from which you can select the value you want. That method works fine without it incorrectly stating 'You can't leave this blank'. You can now save your item.

@Frank-Ove Kristiansen 

 

Same issue here with a customer. We figured out, that this seems to be related to the "Modern Experience" - changing back to "classic" and we can fill the form without a problem or any strange error-messages.

Hope someone will find a solution for that - makes no sense to switch to classic view :(

@Frank-Ove Kristiansen 

 

I checked today (1st May 2019) and this issue seems to have been resolved. Is everyone else finding this is the case?

 

Regards,

 

AJ

@ashokjingar,

I tried recreating the issue today, but was unable to. So it might seem that this has been fixed.

@ashokjingar i can also confirm that the issue no longer persists for my customer. Great :)

@Dominik_N 

 

Unfortunately this still appears for me.

We have the same issue in a SharePoint Online based Document Management System that has a set of required managed metadata properties. It looks if the value is there, yet the system complains with message: You can't leave this blank.

The issue does not occur in Classic SharePoint.

The issue does not occur when using the File--> Info --> Properties in Word app.

The root cause of this is unclear to me. We have filed a Microsoft Premire Support ticket on this.

Hello @Carry4IT Megens did Premier Support provide a solution, I am seeing the same problem, but not if save the file as Rich Text Format. But even if I save that file into the same (new SharePoint online library) as .docx the managed metadata column will not save changes. Another interesting fact: There is another managed metadata column using the same term set, changes to that column do save!?!?!

Clearing 'custom XML' as explained here, https://techcommunity.microsoft.com/t5/sharepoint/document-column-metadata-not-saving/m-p/1309256, did not work. Note, this particular file has been migrated from a SharePoint 2010 library to SharePoint online (but other files in the same library do not have this problem).

@Tony BROOKS no, not really. Thanks for the suggestion to try Rich Text Format, not really a solution... Keep hammering that Microsoft door, until they acknowledge there is an issue in the Modern implementation of this and solve this thing. Really annoying!!

Thanks @Carry4IT Megens. Agreed, if Microsoft have not said there is a soluton what are we supposed to do for our customers?!
This seems to be an issue if the metadata field name had a space in it. When creating new fields don't add any spaces at first. Then go back and rename the file with the space in it after. This should fix your saving issues. It's an annoying bug that has existed for years.... really can't believe MS hasn't fix it yet.
Too late, fields have been created in the past with spaces in them and now used in 50k document or so. So going back is not an option, would you agree?
But those fields are technically renamed under the hood, like "Published_x0020_Version" or "Publishing_x0020_Date" so no more space involved.
I suspect the issue also has to do with multi valued managed metadata fields.
The bug is in Office and the Property Pane. It also has issues if special characters are used in the field name. It has nothing to do with the multi value type. My suggestion to you is to create a new field with the same name just no spaces.... use Power Automate to copy the value over from the broken field to the new one. Then delete the old one out of the content type and list. Then update the name. It's annoying but the only solution if you want people adding metadata through the Office Desktop App with the least resistance.

Unspoken rules of SharePoint:
1) Never create sites or columns with Spaces... rename them after.
2) Never use special characters like \ or - in the field names.... Office cant use them as linked Quick Parts if you do.
Thanks for the quick reply. Aww, no! Why does Microsoft always make things so difficult. Do not allow spaces. Period. But no, sir, now halfway somewhere things break...