SDM 17.3 RU17 - list excel export as .xlsx does not work

[Peter Schmidt]

Hi,
after upgrading to RU17 we tried list-export and it's still .xls

NX.env has:  @NX_USE_LEGACY_EXPORT=No
AND yes, we have restartet SDM ;-)

In search_filter.js (which is included to std_list.js) I found:
// NX_USE_LEGACY_EXPORT="Yes" or "" means that we want to export as XLS,
// if it's set to "No" it means we want to export as XLSX
if (ahdtop.cfgUseLegacyExport.toLowerCase() == "no") {
definition = "1003";
list_name += "|INTERFACE|XLSX";
}

So, as described in post install steps, it should work. But it does not.

No errors in stdlog:
Connecting client pdm_exporter-xxx.de-#3748
Connected to server xxx.de (domsrvr)
Export (pdmweb:xxx.de#357546e:1...:-7fff-8456-1) started for Userid(sxxxn) Factory(aty)
Export (pdmweb:xxx.de#357546e:1...0:-7fff-8456-1) completed after (0.71) seconds.

What else has to be done?

Regards,
Peter

[Peter Schmidt]

Hi,
this thread returns multiple times because it was posted half an hur later than I clicked SAVE.
How can I delete no longer used threads?

Regards,
Peter

[Peter Schmidt]

Hi All,
the reason had been easy to solve.
It's not enough to restart SDM-Service ...
You also have to restart xflow-service ...

Now.xlsx-Files are created.

Regards,
Peter

[Richa Pathak]

Hi Peter, 
xFlow restart is not required for the changes to come into effect. 
We suspect the restart might not have happened properly. But good to know the export is working as expected now.

[Giovanni Tosatto]

Hi,
we have similar problem with the export in xlsx format.

in the stdlog when we try to do an export we see this error:

export No matches found for definition file (1003) .

at the moment we have set th NV variable  @NX_USE_LEGACY_EXPORT to "Yes" and the export in .xls format run , but we need to activate the .xlsx fromat in our customer enviroment.

thanks




------------------------------
Giovanni Tosatto
------------------------------

[Hemalatha Simhadri]

Hi,

Can you check the contents of the table usp_exlist_format in your database? 


Run the query as "SELECT *, usp_exlist_format.id from usp_exlist_format" and see if there is an entry with id 1003 to support xlsx format or not? 
If not we need to update this table. 

Necessary dat file is delivered as part of 17.3RU17 and ideally it should be executed as part of post installation steps. 

From the command prompt go to directory $NX_ROOT\data\ and execute the command as below to update the usp_exlist_format table.

pdm_load -f r17_3_17_insert.dat

Once pdm_load is successful, verify the issue.

Hope this helps.

Thanks & Regards,
Hema.

[Peter Schmidt]

Hi Hema,
in our environment exlist_format is complete.

xlsx is created - BUT when opening the xlsx we get an error:

'we have recognize a problem with some contents in 'export xlsx. Shall we restore as much as possible? If you trust the source of the worksheet, click on yes'

After clicking yes excel sheet is opened with another error:
Repared part: /xl/worksheets/sheet1.xml-Part with XML-Error. Error loading. Line 2, column 0
....

Regards,
Peter

[Paul Coccimiglio]

Peter..........

RU18 contains two fixes regarding the XLSX SDM export.

Can you apply RU18 and see if the issue is resolved?

If you cannot install RU18, please provide your SITEID and I will open a Support Case on your behalf to provide a test fix.

------------------------------
Paul Coccimiglio
[JobTitle]
[CompanyName]
------------------------------

[Peter Schmidt]

Hi Paul,
I've received fix and it works fine.

All, woh con should use RU18.

Regards,
Peter

[Domagoj Hrzic]

Hi Paul,

I've installed RU18, and when selecting export I'm getting an error "TypeError: ahdtop.cfgUseLegacyExport is undefined" in the console:
Any idea what it could be?
Regards,
Domagoj

[Sebastian Nagy]

Hi Domagoj.

Do you have ahdtop.htmpl customized? The ahdtop.cfgUseLegacyExport is supposed to be defined in ahdtop.htmpl.

Regards,
Sebastian

[Domagoj Hrzic]

Hi Sebastian,

no, none of these files (load_cache.htmpl and/or std_head_include.htmpl, ahdtop.htmpl ) have been customized.

Regards,
Domagoj

[Sebastian Nagy]

Hi Domagoj,

Based on the screenshot that you shared the ahdtop.htmpl is quite old, Feb 1st 2022.

SDM 17.3 RU17 was released arround Sept 2022. Are you 100% sure that RU17 was property installed? There should have been a HYD-696 folder in the REPLACED folder. The build number for 17.3RU17 is HYD-696.

But it still seems you got some patch that delivers new-er JS files, without getting the htmpl files.

I would recommend to open a Support case and we'll be more than happy to help you. I can't ask you to provide the history file in the community.

Regards,
Sebastian

[Sebastian Nagy]

Hi Domagoj,

I checked the ahdtop.htmpl that we ship in 17.3RU18, in another thread I see you have RU18 installed, and I can confirm that I can see:

var cfgUseLegacyExport="$env.NX_USE_LEGACY_EXPORT";

The timestamp of ahdtop.html in RU18 is Nov 3rd 2022.

Regards,
Sebastian