No response when export EXCEL from Mapping in FDM

Dear All,
I am using FDM 11.1.1.3. And, install as usual.
I cannot export Excel from Mapping in FDM.
The screen is just keep waiting for long long time.
How to fix it? Thanks for all.
Karen

We did have a bug in older versions of smartview where it was not possible to deinstall it. Smartview was removed but any attempt to install a new version failed. This was because Smartview creates a Registry entry in:
HKEY_CURRENT_USER\Software\Microsoft\Installer
and adds the key
C:\DOCUME~1\USERNAME\LOCALS~1\Temp\_is3EA\
which then prevents any newer version of SmartView to be installed
I looked on my machine and the is3EA file does not exist, however there is an installer file called isA.exe
The registry entries for smartview are found under HKEY_CURRENT_USER\Software\Hyperion Solutions\Hyperion Smartview - maybe you could try deleting these entries? --> solution works.
Edited by: user9378541 on 27-sep-2010 2:45

Similar Messages

Missing export options when exporting Excel from the CRXIR2 CrystalReportVi

Hi!
This is an app ported from CR9 to CRXIR2/Net. I print to screen using the CrystalReportViewer in a Windows form. Export button is enabled, but when I click and export to say "Excel", no further dialog is shown. Ie I never get the one wherev you normally would change options like Column widths and page breaks. What have I done wrong?
Exporting from the Crystal designer app itself works, ie I get the additional dialog.

OK. I had 11.5.12.1838 installed which is R2 Sp6. Or is it 2A? Your blog says "Check the version. It should be 11.5.12.1838."
Edit:
The behaviour is also different. If I run the CR designer and select export, I get a window, much like the one in CR9, ie where I can select destination etc. From the viewer I get a window, much like the ordinary Windows save dialogue and from there I cannot change any options. All I can do is select export type.
To add insult to injury the dialog defaults to *.rpt, even though I have done a:
m_Report->ExportOptions->ExportFormatType = CrystalDecisions::Shared::ExportFormatType::PortableDocFormat;
before passing the report to the viewer.
To elaborate: This is what I would like to happen:
http://www.pedago.fi/dalton/diverse/export1.png
Then:
http://www.pedago.fi/dalton/diverse/export2.png
But what I get is:
http://www.pedago.fi/dalton/diverse/export3.png
Edited by: Anders Gustafsson on Nov 10, 2011 9:03 AM
Edited by: Anders Gustafsson on Nov 10, 2011 10:17 AM
Edited by: Anders Gustafsson on Nov 10, 2011 12:53 PM

Why would I want to change JPEG quality of photos when exporting them from iPhoto?

Why would I want to change JPEG quality of photos when exporting them from iPhoto? Changing the quality of the print changes the size of the saved file and thus impacts the speed at which it is moved on the internet. But other than size of the file, what is the advantage of changing the quality?

I have no idea why you would want to do anything
Some people want lower quality to reduce file size for different reasons
It is an option - if you do pot want to do that do not use that option
LN

CS5: Bug when exporting directly from PPro with hardware MPE?

For the record, I'm using:
A GTX-480 (unsupported)
The hardware MPE-enabling hack (unsupported)
The latest version of the nVidia drivers (257.whatever)
I discovered an issue, of sorts, when exporting directly from Premiere CS5, versus using the "Queue" option to send to AME. I was exporting from an NTSC DV Standard sequence to a 320x240 H.264, in which I had enable cropping and trimmed a bit off the sides and top and bottom of the source; the Output tab was summarily set to "Scale to Fit". With hardware MPE enabled in the Project Settings, the export would be the proper final dimensions (320x240), but any area that was cropped off was instead padded with black. The actual video content was then squeezed and malformed into the area not occupied by the black bars.
I found that, if I disabled hardware MPE or sent the export through AME by use of the Queue button (instead of Export), then the export was performed properly--the video was cropped correctly and then the video stretched to the borders of the exported video, maintaining the desired aspect ratio.
As I mentioned at the outset, I'm breaking a couple rules and perhaps tempting fate with others, but before I go about rolling back my drivers and the like, has anyone noticed a similar issue?
ADDENDUM: By the way, the export doesn't need to come from a sequence. If I load up a source clip into the Source Monitor, and export from there using the process outlined above, I get the same issue. This would seem to indicate, to me, that this is due to some incompatibility with my card, its driver and hardware MPE...

Did he demo renders or exports?
About 11 minutes in, he [Dave] demos accelerated H.264 renders.
Harm Millaard wrote:
AFAIK MPE only works with renders, not with encoding.
Well, he did both, actually--but the quote above is a typo on my part. I meant to say "exports" or "encodes." The last couple minutes of the aforementioned demo video are dedicated to exporting a sequence directly from Premiere, and having the benefit of hardware MPE. That's where I'm getting the issue I've outlined above; with hardware MPE enabled, and using the "Export" versus AME "Queue" button/function, I get the strange black outline. With software MPE or through AME, all is well.

Trouble maintaining original "date taken" info and metadata when exporting TIFFs from original CR2 files.

When exporting TIFFs (from original RAW), I noticed my metadata said the "date created" was the day of export. I want to be able to access the date the original image was taken as opposed to the day I exported it. Is there a way to maintain original date of image taken in my info? I couldn't seem to find it after I exported my TIFFs...

I just tested this with LR 5.5 Mac OS 10.9.3 and it works correctly for me.
To troubleshoot your problem:
1. Which version of LR and which platform (Mac, Windows)?
2. Which tool or command are you using to examine Date Created of the exported TIFF?
3. Upload a sample TIFF showing the problem to Dropbox or similar and post the URL here. This will allow us to take a look in detail.

How can you keep the highest iphone 4s Video quality the same when exporting it from iMovie.

How can you keep the highest iphone 4s Video quality the same when exporting it from iMovie.

InDesign's PDF export engine does not transcode your videos, they are embedded exactly as they were in the original file. The Flash Player runtime which displays video inside PDF files may not show a perfect match to Quicktime etc. because most video playback tools aren't designed for a color-calibrated workflow, but they should be close.
The playback quality (blocking and aliasing) will be affected if the clip is not playing at 100% (screen pixels != video pixels) and in PDFs with the standard video player widget, that will only ever happen when you use 'floating window' mode. PDF pages have physical dimensions, so viewing them at "100%" does not make them match screen pixels.
If you don't mind the video clip being smaller than the media annotation in which it's playing, then use my free upgrade to the Acrobat playback widget - VideoPlayerX - which maintains 1:1 pixel scale until the page is zoomed out too far for it to fit. You can install the widget into InDesign so it's used by default when exporting.

Problem when exporting Query from Web template to Excel Sheet.

Hello,
Im encoutering a problem when im trying to export query output from web template to excel sheet.
A popup windown appears when excel sheet opens which reads.."problem cameup in the following areas during load : Cell Value".The report layout appears to be fine but the totals shows unwanted values starting with * followed by number.
Any valuable inputs, what could be the problem. where can i rectify the same.
Regards
Ellora

Hello A K,
Thanks for ur time and response but the option u mentioned did not serve my purpose.
The problem seems to be only with pirticular cells.As mentioned earlier the layout appears properly..all the values are seen..but the end result..totals are disturbed.
eg: If the report shows in template the total value :20,668,554...when exported the values is shown as **668553.88000000600000.
So what could be the problem ? any template setting ? global setting to look at ?
Regards
Ellora

Error when trying to export excel from Chrom

Hi,
I get the following error message when i try to export the excel from Chrome browser. Has anyone encountered this error when trying to export from Chrome ? can you please give me the solution.
Thanks.
Error message:
To export a list, you must have a Microsoft SharePoint Foundation-compatible application

Hi,
From your description, when you export a SharePoint list to excel from chrome, you get an error.
In my SharePoint 2013, when I export a SharePoint list to excel from chrome, it works fine.
For your issue, make sure the excel client have been installed in your environment.
To narrow down the issue, I would like to confirm the following information:
To check whether the issue is related to the browser, I suggest you to do a test in other browsers, such as IE and compare the results.
What version is your office client? office 2013 or 2010? 32bit or 64 bit?
Besides, here are some similar posts, you can take a look at:
http://community.office365.com/en-us/f/172/t/160015.aspx
https://social.technet.microsoft.com/Forums/office/en-US/5ffbeb9e-6eb1-41c2-8141-edab6039bbde/to-export-a-list-you-must-have-a-microsoft-sharepoint-foundationcompatible-application?forum=sharepointadminprevious
I am looking forward to your reply back.
Best regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Error when exporting reports using MAPI

We created a .NET class that wraps CR 2010 .NET Crystal Reports functions and made it COM visible. This class is used to create a COM object in a js script which in turn used to export reports to a PDF file with the destination MAPI.
It exports reports just fine without any errors however if prior to instantiation the exporting class we instantiate a class that has nothing to do with the Crystal Reports functions, our exporting object throws u201CExternal component has thrown an exception.u201D error when exporting. It appears that it has something to do with the SideBySide feature. I was wondering if somebody knows what causes this and if there is a way to fix this problem.
Thanks for your help!
 
 
Below are 2 procmon.exe outputs, the first when exporting works and the second when it doesnu2019t
 
 
 
1) Procmon.exe output when exporting works fine
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 7:16:30.7403615 AM test.exe 4396 FASTIO_QUERY_INFORMATION C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Image Base: 0x79260000, Image Size: 0x1073000
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryNameInformationFile, Name: \Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest NAME NOT FOUND Length: 20
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 
 
 //////////////////////////////////////////////////////////////////////
 2) Procmon.exe output when exporting doesnu2019t work, notice that it tries to open MSO.dll at the same location as in the output above but fails, it tries then to open it at several other locations and fails
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll FAST IO DISALLOWED
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll FAST IO DISALLOWED
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\SysWOW64\MSO.dll FAST IO DISALLOWED
 C:\Windows\SysWOW64\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\system\MSO.dll FAST IO DISALLOWED
 C:\Windows\system\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\MSO.dll FAST IO DISALLOWED
 C:\Windows\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

I tried to run exporting code in a .net application and got the same error. I first created the COM object that causes the problem and then ran exporting CR functions. It works fine if I run the code without creating the COM object.
Below is the code I used.
 Type objClassType = Type.GetTypeFromProgID("ebms.main");
 object objMain = Activator.CreateInstance(objClassType);
 try
 object[] p = new object[4];
 p[0] = "C:\\ebms\\co1";
 p[1] = "C:\\ebms\\co1";
 p[2] = "Administrator";
 p[3] = "";
 objClassType.InvokeMember("LoginToCompany", System.Reflection.BindingFlags.InvokeMethod, null, objMain, p);
 catch (Exception ex)
 this.RPTDoc = new ReportDocument();
 this.RPTDoc.Load(@"C:\\Users\\Paul\\Desktop\\AR Customer List.rpt");
 PdfRtfWordFormatOptions pdfOpts = ExportOptions.CreatePdfRtfWordFormatOptions();
 MicrosoftMailDestinationOptions mailOpts = ExportOptions.CreateMicrosoftMailDestinationOptions();
 ExportOptions exportOpts = new ExportOptions();
 pdfOpts.UsePageRange = false;
 exportOpts.ExportFormatOptions = pdfOpts;
 mailOpts.MailMessage = "something";
 mailOpts.MailSubject = "something";
 mailOpts.MailToList = "emailaddress";
 exportOpts.ExportDestinationOptions = mailOpts;
 exportOpts.ExportDestinationType = ExportDestinationType.MicrosoftMail;
 exportOpts.ExportFormatType = ExportFormatType.PortableDocFormat;
 try
 this.RPTDoc.Export(exportOpts);
 catch (Exception ex)
 MessageBox.Show(ex.Message, "Error", MessageBoxButtons.OK, MessageBoxIcon.Error);

Error when exporting file from LR5.2 - file created

After updating to LR5.2, I receive an error when exporting files to another disk drive. a file is created, but a warning appears "Unable to Export: "An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute". I also have CC iunstalled for other applications, but originally installed LR5 as a standalone Adobe application. I tried removing the program and reinstalling through CC, with no change in this behavior.

The answer is in the thread:
http://forums.adobe.com/thread/1303578?tstart=0

Can't Choose Page Range when Exporting PDF from InDesign

Hi! Ever since I upgraded to CS6 via your subscription, I can't choose a page-range when exporting to PDF from InDesign (8.0.1). Here's a video demonstration of the problem so you can see the bug in action: http://screencast.com/t/kYR1ACtNi
Are you aware of this bug? If it's not a bug, how do I fix it?

Alternate layouts are used for things like horizontal and vertical orientations of the same layout for use on tablets. I suspect there's some coverage in the Help files -- being a print guy I don't mess with them.
It may be that you only have one layout and ID just shows you that one inthe dropdown. I can't recall that I ever used the dropdown to try to select the range -- I always just type what I need in the field.

Colour loss when exporting jpeg from Aperture 2.1

I'm having a problem with colour loss in images i'm trying to export to a website.These are jpegs that have been worked on as RAW in Aperture,when exported to desktop and viewed in preview there is no colour loss at all, but when viewed on the site the colour saturation seems very dull and lack lustre - any ideas?? I have checked all the export presets (been going through all the posts to see if i could pickup anyone else finding the same) and they are all at the same settings. Thanks

Go to the tools menu and then assign profile. Choose the display profile that your monitor is using. This will effectively stop preview from doing any translation to your monitor. See if this matches what you are seeing when you upload to the web. If it does then somewhere in your upload, process, web server chain the profile is being removed from the jpg or the browser you are using ignores color profiles (most windows browsers ignore image color profiles, that's why adobeRGB profile images look like crap to most windows users when viewed in Explorer)
Ps if this is the case nothing is wrong you are just getting a preview of how most windows users will see your image on the web. Adjust to taste.
RB
Ps. Some good info and humor here:
http://www.rwboyer.com/RBDesign/Blog/Entries/2008/4/16_Color_Management_and_Other_Stupid_InternetTricks.html
Message was edited by: rwboyer

When exporting video from Premiere Pro?

When exporting a video from Premiere Pro it makes a .m4v file instead of .mp4, even though it saids in the Premiere Pro that it will make a mp4 file - and I can't use them afterwards. It has been there after I have updated last time.

Also, make sure that you check the box marked "Export Audio" if you want a MP4 extension.

Xcelsisus connections mappings get lost once we export excel from xlf file

Hi All,
I am creating a dashboard in xcelsius 2008. I have around 50 live office objects and hence 50 live office connections in the xlf file. When I exoprt the excel from the xlf file and when i re- import the excel all the old live office connections get lost. is there any way to maintain these live office connectons?

Which SP are you on. The problem could be with java web start. You may re-initialize java webstart from Administration option and clear the contents.
Regards,
Prateek

When exporting versions (from DNG-to JPEG org size) they get very smal?

when exporting versions in aperture (from DNG-to JPEG org size) they get very smal? Why cant they stay the same size and kvalety as the DNG?

How are you exporting? If you are dragging the image out of Aperture you get the preview, you are not exporting the version.
If you are exporting then the most likely reason for what you see is the setting on the Quality slider. Remember JPG images are compressed and you will always see a difference between the original and the exported JPG.
regards

No response when export EXCEL from Mapping in FDM

Similar Messages

Maybe you are looking for