Ever since the FMP 18 and FMS 18 server upgrade the import GUI has been changed and no shows no fields to map as if there is no columns in the table?
Anyone else experiencing this or know a fix?
Import Screen
Table
Filemaker have noted this has a bug but no fix yet,
Only solution is to edit the script on FMPA17 or below..
I had the same issue..
Source
Related
Situation: I'm importing an xlsx file with PROC IMPORT and wanting to send the data OUT to a new netezza database table.
My issue: SAS appears to run fine, but the log shows a completely different table name was been created with a libref that I'm not using (and this libref is cleared).
LIBNAME abc sasionza server=server database=db port=123 user=user pass=pass;
PROC IMPORT
OUT = abc.DesiredTableName
DATAFILE= "my/excelfile/file.xlsx"
DBMS=xlsx
REPLACE;
SHEET="Sheet1";
GETNAMES=YES;
RUN;
This "runs" just fine, or so it appears to. I check the log and I see this:
NOTE: The import data set has 11 observations and 7 variables.
NOTE: xyz.ATableCreatedDaysAgoInAnotherProgram data set was successfully created. NOTE: PROCEDURE IMPORT used (Total process time):
real time 0.55 seconds
cpu time 0.02 seconds
I thought, hmm, that is weird. libref xyz is actually cleared, so I couldn't possibly use it, and ATableCreatedDaysAgoInAnotherProgram is a tablename used in a completely different SAS E-Guide program I have going on.
Sounds like a memory or cache issue. So, I close all instances of SAS E-Guide and fire up a new one. I created a new program that only has my desired lines (the code listed above).
It runs, and I get the following log as a result:
NOTE: The import data set has 11 observations and 7 variables.
NOTE: WORK._PRODSAVAIL data set was successfully created.
NOTE: PROCEDURE IMPORT used (Total process time):
real time 0.55 seconds
cpu time 0.02 seconds
I will note that this is the first time I've actually tried to use PROC IMPORT to send something directly to a netezza table. Up until now, I've always imported files into WORK and worked with them for a bit before inserting them into a table in a database. I thought that maybe this is a SAS limitation I may not be aware of, but the SAS documentation for PROC IMPORT (https://v8doc.sas.com/sashtml/proc/z0308090.htm) says that you can specify a two level name in the OUT statement, so I feel that this should work. If it can't work, then I feel that SAS should error out instead of randomly creating a table name that I'm not even executing in my code.
Summary (tl;dr): Can you PROC IMPORT directly into a netezza database table using a libref? And if you can't, why is my code executing and producing text that isn't even related to what I'm doing?
Thanks, everyone!
The Solution: A column in the xlsx file being imported had a space in one of the column names... Simply removing the space in the column name and saving the changes to the xlsx file allowed for the PROC IMPORT code above to be executed flawlessly with the desired results being imported into the named netezza table.
NOTE: This fixed my problem, but it does not explain the SAS log showing text executing that wasn't actually in the code to be executed.
Sounds like you should report the issue with not getting a working ERROR message to SAS.
To make sure that your SAS/Netezza tables do not have variable names with spaces in them change the setting of the VALIDVARNAME option before running your program. That way PROC IMPORT will convert your column headings in the XLSX file into valid variable names.
options validvarname=v7;
libname out ...... ;
proc import out=out.table replace ...
I have 5 Webi reports and all these reports works fine. Out of the 5 reports , 3 reports i could export to available mode. But the other 2 reports too i can export to pdf or excel or excel 2007. Here come the problem. When i export to excel or excel 2007, i do not get the exact structure of the report, like the table and the values. What i get is complete blank with Report Tab name.
Have anyone gone through this kind of problem? If so please help me if i went wrong for this 2 reports alone.
Thanks
Niki.
First select the Table and Check in Vertical Table setting and if you see any Blank variable added into report, please delete.
So that report will extract without any error.
You can set preferences if you want to optimise export to Excel to preserve formatting or preserve data. Try configuring your preferences to preserve data or preserve formatting when exporting to excel and experiment.
Exporting to excel can be tedious, your webi report needs to be optimised to properly export to excel and preserve formatting and data
I have created a crystal report with datasets(xsd) , it is working fine. Then i added a new field in xsd and when i open the field explorer it do not show that field, i added source again through database expert but still it is not showing that field. Any other person faced such issue then please help.
After waiting a lot for right answer and searching on internet i tried different options by myself and the problem was solved by right clicking on database fields and then click on verify database. If some one have some better option then please suggest.
I had the same problem and resolved it by adding parameter input and running the report from the designer. Crystal report popped up and said that it was fixing the report and refreshed the connection to the database for the most current fields.
I had a similar easy where Log on or Log off server and Verify Database wouldn't update the database fields list in Crystal Reports. The only thing that worked for me was to physically move the typed dataset to a different location. After creating a new connection within Set Datasource Location I updated the datasource and there it was....
Sap Crystal report has a problem while refreshing database changes to crystal report. I found this solution and it works like a charm:
First go to refresh data base option and then it will ask you to enter parameter values to the stored procedure
then without passing any values just press escape button it will suddenly ask you to confirm the changes made to database when you do it on second time it will say database is up to date
Don't forget to rebuild your solutions before validate your database.
Restarting the Machine did the trick for me.
Some data types in dataset can't show in crystal reports try to change data types ( example don't use System.DateTimeOffset use datetime only)
Verity database in database fields
If your DataSet (.xsd) came by "Add Existing File" and not create one, then you will encounter a problem like mine. to fix this:
-Find the DatasetName.xsd file and all of its name-like file . Copy it EXCEPT THE DESIGNER (DatasetName.Designer.cs) and paste it somewher, you will re-paste it later
-In your VS. Delete the DataSet (xsd File) in your project by right click it in your Solution Explorer. This will delete any traces of file.
-Re-paste the files that you copied in the same location. Then in VS. And add the xsd file that you re-paste.
-Then you can now add columns. And it will update the DataSet, and also the Crystal Report will see the updated column
Reason: For i-dont-know-what-the-heck-happened, if you include the designer file then add it in you project, then you add columns to it, the VS will create new designer.cs file instead of overwriting the existing file. So the column registers only in original but the newly created one only recognized as valid (which is no traces of new added column)
You can press F5 to see preview, if crystal report find out new fields it will verify all field in database, and your new fields will appear.
Hope this will help you!
Log off from server, then verify database, that did the trick for me!
By just updating the entire datasource location did not work for me. I had to expand the source location and then update the individual table. Hope this helps someone.
Right click REPORTDATASET then select Set Datasource Location.
click database files and select your existing *.xsd. then you will see REPORTDATASET.
select it.
update
close
Now you will be seeing the new fields in your *.rpt :)
I use the following technique:
Select datadese expert in crystal report
Select previous added datatable.
Press "<<" to remove it from reporting, its related columns are removed from report automatically.
Then select Project Data>>ADO .Net DataSets>> your updated dataset
Press ">>" to add and click the OK button.
New added field also shows in dataBase fields and then added in report.
I am having a problem with crystal reports because the records are not being displayed correctly. Below is the screenshot of the comparison between the crystal report output and the query from the database.
I would like to ask for a work-around or solution to this. I tried deleting the object and placing it again but it didn't work.
The telephone number is not pulling from the field you have highlighted in your screenshot. You can see the name is pulling from that field as it has the trailing /
If the telephone number is pulling from the FAPT_TELNO field i'm a bit puzzled why the A is being translated to 0. Are you able to attach the report with the data saved?
I found the solution, but still find it weird.
All that I have to do is to add this code and it will be back to normal
lower(mtel_picnm)
But I don't know why I need to do that. Any help on this? Just add in the comments to enlighten me.
I have excel sheet and I have 5 columns all are of type VARCHAR's.
I have a Table called Details and has 5 columns all of type VARCHAR's.
I have to import the data from Excel to table every day.
I am manually copying the records from excel and pasting them into the sql table. This approach is easy and quick.
But I want to make it automated.
Can I do it through the coding by giving the location of Excel Sheet.
I am using SQL 2005 and Excel 2007.
Any suggestions or directions please.
Thank you.
You can use Integration Services to import excel files automatically, here is a good example:
http://www.techrepublic.com/blog/datacenter/how-to-import-an-excel-file-into-sql-server-2005-using-integration-services/205
You can also use Import/Export Wizard within SQL Server 2005 as well, which does the same job and also allow you to save it as a SSIS package.