Erro 225 - Falha no Schema XML do lote de NFe com mensagem formato invalid
Pessoal, boa noite.
Estou me deparando com um problema de validação de NFe no Sefaz GO, onde está retornando o erro 225, mas quando verifico o retorno tenho a mensagem de que o formato não é valido (abaixo print) . Verificando o dado, não tem nenhuma divergencia entre os demais valores. Alguém ja se deparou com este erro?
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:nfeRetRecepcaoResponse2 xmlns:ns1="http://sap.com/xi/NFE/006">
- <ns1:nfeRetRecepcao2Result>
- <ns2:retConsReciNFe xmlns:ns2="http://www.portalfiscal.inf.br/nfe" versao="2.00">
<ns2:tpAmb>2</ns2:tpAmb>
<ns2:verAplic>GO2.0</ns2:verAplic>
<ns2:nRec>521000004377506</ns2:nRec>
<ns2:cStat>225</ns2:cStat>
<ns2:xMotivo>Rejeição: Falha no Schema XML do lote de NFe</ns2:xMotivo>
<ns2:cUF>52</ns2:cUF>
<ns2:cMsg>225</ns2:cMsg>
<ns2:xMsg>cvc-pattern-valid: Value '5499.00' is not facet-valid with respect to
pattern '0|0.[0-9]{2}|[1-9]{1}[0-9]{0,12}(.[0-9]{2})?' for
type 'TDec_1302'.</ns2:xMsg>
</ns2:retConsReciNFe>
</ns1:nfeRetRecepcao2Result>
</ns1:nfeRetRecepcaoResponse2>
Edited by: Fernando Ros on Apr 22, 2011 8:03 AM adicionando tag code para visualizar todos os caracteres
Bom dia Carlos,
Em sendo a Sefaz GO a inconstância não me surpreende, mas a de se estar atualizado, principalmente com o removedor de caracteres e validador ativo para evitar a chance do programa da Sefaz se confundir que é o que parece estar acontecendo... Está apontando o problema num lugar onde a mensagem apresentada está ok.
Sugiro atualizar o sistema ao SP18 que é o necessário para trabalhar de forma saudável com layout 2.0
Atenciosamente, Fernando Da Rö
Similar Messages
-
Error 70 - Código do status 225: Rejeição: Falha no Schema XML da Nfe.
Bom dia grupo!
Nós estamos atualmente recebendo a seguinte mensagem de erro da SEFAZ relacionado aos batches que nós enviamos: Error status 70 "Error from the authorities" and Código do status (Status Code) 225: Rejeição: Falha no Schema XML da Nfe.
Nossa configuração é 46C com muitos OSS notes aplicados (veja abaixo)
Nós estamos realmente parados neste momento e não temos nem ideia de onde começar.
Atenciosamente,
Marc de Ruijter
OSS notes for NF-e phase 2
989115 Nota Fiscal Electronica (NF-e) - Overview Note
852302 Implementation Overview ISS 2004 - Legal Change MP135/LC116
759965 New Condition Formulas for MP-135 and ISS 2004
747607 Basic Customizing for MP135 and ISS legal change Brazil
980214 DDIC changes: PIS / Cofins Tax Law and Tax Situation
981123 PIS / Cofins Tax Law and Tax Situation
981687 NFe: For Services in Muncipio Sao Paulo
934846 Syntax error: TYPE-POOL 'SXRT' is unknown
979881 Message S 000 in NF writer when mandatory fields not filled
980213 Nota Fiscal Electronica (NF-e) of SEFAZ - Phase 2
1037070 NF-e of SEFAZ - Phase 2, Enhancement 01
1014600 No output found for the Nota Fiscal
1052575 NF-e of SEFAZ - Phase 2 / DDIC changes after shipment
1043688 NF-e of SEFAZ - Phase 2, Enhancement 02
1062468 NF-e: Multiple volume structure for XML file
1062251 NF-e: Extension of BADI Interface FILL_HAEDER
1070261 NF-e of SEFAZ - Phase 2, Enhancement 03
1094041 NF-e of SEFAZ - Phase 2, Enhancement 04
1000130 Public System for Digital Bookkeeping (SPED) - Overview Note
1008306 SD: Manual changes of CFOP for services when ISS tax applies
998194 Missing ISS Tax Situation in the Nota Fiscal
1047606 SD/Brazil: Using of error log during Nota Fiscal creation
120449 SD-Brazil Exchange variance error in Nota Fiscal
92383 LSA:BR:SD: Tax laws in return nota fiscal
689157 Nota Fiscal Split and number of Packages
987882 ISS Tax Law (field J_1BTAXLW3) not copied from sales order
989965 CFOP redermination in the delivery document not working
909835 Message 8B 679 raised during the delivery process
337554 SD: No. of packages in Nota Fiscal
533046 Repair order inconsistent to object list
920330 Error when changing the tax codes in a sales order
998195 PIS/COFINS/ISS Tax Law and Tax Situation in SD
104606 EDI/IDoc: Mapping IDoc types to ANSI X12
1094041 NF-e of SEFAZ - Phase 2, Enhancement 04
1105588 J_1BLFZF: Runtime error OBJECTS_OBJREF_NOT_ASSIGNED
OSS notes for XML ver 1.1 and NF-e phase 3
1065334 NF-e: Extension of BADI Interface FILL_ITEM with tax table
1068615 NF-e: Extension of BADI Interface with SD document flow
1079826 NF-e: BAdI Interface Enhancement for NF Messages
1069919 NF-e: Partner in Block E should always be main partner
1090279 NF-e monitor: automatic refresh upon user actions
1093252 NF-e: ICMS tax situation in XML File and DANFE
1113127 NFe: New XML Layout - Version 1.10
1114348 NF-e - xNFe integration - backend
1122294 Send/resend NF-e: fill VBFA for BAdI item method
1124075 NF-e: Serie not taken from Contingency NF-Type
1144194 NF-e: Cancellation/Skipping Reason
Bug Fix notes for NF-e BAPI.
1049946 NF-e: Adaption of Nota Fiscal Bapis
1147934 NFe: Random number should not be generated for incoming NFes
1150733 NFe: Randon number and check digit not cleared
1154995 NF-e: NF BAPI - enhancement for NF-e processing
1158622 NF-e: NF BAPI - no input of random number possible
Bug Fix notes for Contingency process
1158612 NF-e: Wrong partner in Block-E for Entrada
1240212 NF-e: One time Vendor data not transferred to XML file
1255450 NF-e: Jurisdiction code for one time vendor / customer
1257030 NF-e: Country Name for one time vendor / customer
1069018 Cancellation of incoming NFe shows error J1B_NFE 003
1070077 NF-e: Protocol number and document status for Denied NF-e
1145148 NFe: Cancellation for Contingency NFes
1152263 NF-e monitor: wrong action status '7' for C-NF-e
1146914 NFe: Synchronous call to messaging system from backend
1149356 NFe: Dump when NFe is cancelled with MIGO
1152081 NFe: Dump when NFe is cancelled with VL09
1153533 NFe: Dump when NFe in contingency is cancelled with VL09
1156116 NF-e: Contingency by stock transfers
1160107 NF-e: Cancellation of contingency NF-e with DOCSTA = 1 or 2
1161347 NF-e: Cancellation of Contingency NF-e - correction
1238648 NF-e monitor: req. action '3' (send) wrong for swtch. NF-e
1165953 NF-e: Numbering Gaps
1244326 NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP
1245425 NF-e monitor: required process step - contingency
1252567 NF-e: Resend of NF-e - rejected or with validation error
1266344 NF-e: Action Indicator for NF-e with validation error
1254565 NF-e: Synchronization of RFC call between ERP and xNFe
1053626 MIRO: wrong document reference in nota fiscal
1073259 NF-e: Transfers - Outgoing NF-e No. not taken by Incoming
1153874 NF-e: GR for future delivery takes wrong NF-e number
1174946 NF-e: Serie not considered for duplicate NF-e number in MIRO
Miscellaneous bug fix notes
1175538 NF-e: Reference between NF and NF-e
1244881 NF-e: Mixed scenario in MIRO shows error 8B219
1257422 MIRO: Error 8B 219 by posting of reference invoices
1150843 NFe: Text for cancel reason not transferred to XML file
Bug Fix Notes Group 2
1059699 NF-e: Reference between NF and NF-e
1139062 NF-e incoming: Posted via J1B1N -> Wrong Document Status
1144199 NF-e: SD Billing and Contingency
1145089 NF-e: Cancellation despite rejected cancel request
1149787 NF-e: Wrong status-code text in NF-e history
1151112 NF-e: cancellation-reason text gets lost (pre req of 1150172)
1150172 NF-e monitor: selection leads to dump
1068379 Creation of Billing document issues an error 8B 145 (pre req of 1145089)
1152842 NF-e: cancellation reason does not work
1154700 NF-e: Random number & check digit not stored in active table
1073145 PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
1082527 Missing PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
997868 VL02N: CFOP, tax laws not copied from delivery (error 8B148) u2013 (pre req of 1155231)
1155231 PIS/COFINS tax law in NF/NF-e by split valuated material
1155424 NF-e monitor: Menu -> "Check MS Connection" does not work
1159177 NF-e: FUNC J_1B_NFE_SET_STATUS_IN_BACKEND set as Rem.Enabl
1161951 NF-e monitor: "Resend" functionality.
1162232 NF-e: switch to contingency not possible after MSS Update
1162512 NF-e: cancellation reason not initial at first-time call.
1162629 NF-e: creation date gets deleted from NF-e data-base table
1164283 NF-e: SCS '5' - upon authr.to cancel system does not cancel
1165155 NF-e Monitor: BACK (F3) leads to cancellation
1165360 NF-e Monitor: new selection parameter - creation user
1168394 NF-e: Reference document not taken from Nota Fiscal header
1168798 NF-e: User decision for used NF-Type for Material Movements
1171383 NF Writer: Copy NF-e that was switched to contingency.
799445 Nota Fiscal creation: Consideration of local dates (pre req of 1171383)
1104003 NF-Writer: Serie not taken from Reference NF (pre req of 1171383)
1156037 NF-e: NF-Writer allow reference with different NF-types (pre req of 1171383)
1175759 NF-e: central contingency per business place - correction
1239598 NF-e: Random number and check digits are lost in NF writer.
1163888 NF-e: Random Number includes spaces (pre req of 1239598)
1245425 NF-e monitor: required process step u2013 contingency. u2013 applied in bug fix notes no need to apply.
1246700 NF-e: Wrong reference for NF entradas.
1257688 NF-e: Update termination with error J1B_NFE 021
1258021 NF-e: Dump by creation of NF header text for XML file
1258974 NF-e: Monitor report aborts with DBIF_RSQL_INVALID_RSQL
1265172 NF-e - Decouple RFC from DB Update
1285851 NF-e: Cancellation of none authorized documents
1288925 NF-e: References between NF-e and non NF-e
1272677 NF-e: Cancellation for Material Document with serial number (pre req for 1288925)
1247602 NF-e: Cancellation of material documents with serial numbers
1163104 NF-e: Cancel Material documents with initial cancel reason
1293944 NF-e: Cancellation of material documents with batch classes.
1267128 NF-e: Cancellation goods movement with MVT 844 not possible (pre req for 1293944)
1300000 NF-e: Decouple - Contingency
1314856 NF-e: Decouple - Contingency in J1BNFE and VF01 & VF04
1321837 F-e: Cancel of material documents not possible
1092028 NF-e: Protocol number in NF-header overwritten (pre req for 1265172)
1114283 NF-e: cancellation - document status cleared in J_1BNFDOC (pre req for 1265172)
1234053 Local time / local date in NF header and NF-e XML (pre req for 1265172)
1288994 NF-e: Decupling note 1265172 causes error for incoming NF-e (pre req for 1300000)
1297042 NF-e: NF-e number missed in access key after decoupling (pre req for 1300000)
1087535 RFFOBR_A,U:Doc.no should be filled with 9 digits in DME file Applied OSS note 1087535 to the object Z_RFFORIY1 which was copied from RFFORIY1
1097455 NFE: Bank files should accommodate Doc. Numbers with 9 digits
304961 Wrong boleto check digit with carteira data (pre req of 1097455) - Not relevant
336117 Include due date factor in Boleto barcode for A/R (pre req of 1097455) - Not relevant
705726 ITAU: Boleto has negative interest value (pre req of 1097455) - Not relevant
846297 Func Mod - BOLETO_DATA not printing correct nosso numero (pre req of 1097455) - Not relevant
852782 BOLETO_DATA - Corrections of note 846297 for Bredesco only (pre req of 1097455) - Not relevant
1227478 Dump in payment run (F110) when XBLNR is empty
1138278 NFe: Field PREDBC not filled in XML interface structure (pre req of 1149585)
1149585 NFe: CST field required in XML file for taxes not in NFe
1053855 VL02N raises error 8B 053 "Branch not foundu201D
1165696 RFEBBU00: Error in batch input due to changes in Nota Fiscal
1180402 NF-e: BADI methods FILL_HEADER and FILL_ITEM
1180672 NF-e: Gap numbering check doesnu2019t consider the series
1225338 RFEBBU00: Additional changes to the note 1165696
1241922 NF-e: Report J_1BNFECHECKNUMBERRANGES xNFe adaption
1244326 NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP (Applied using other Kintana)
1270813 NF-e: Year not included in the XML file
1247264 NF-e: Error in RFC to /XNFE/NFE_CREATE after note 1241922 (pre req for 1274200)
1274200 NF-e: Numbering gaps report sends SERIE with spaces
1276185 NF-e: Numbering gaps report sends SERIE with spaces
1294917 NF-e: Gap numbering check - several corrections
1324538 Missing address for OT Customer in J_1B_NFE_CREATE_TXT_FILE
1331432 NF-e: Numbering gaps report detects gaps for initial series
1332167 NF-e: Rep. J_1BNFECHECKNUMBERRANGES aborts with error DC 006
1092341 RFFOBR_A,RFFOBR_D: Performance problem while rebate calcula
1237089 RFEBBU10:While uploading ITAU Bank returnfile- Error(F5 170)
1051314 Check Digit missing from Boleto number (pre req for 1306966)
1306966 J_1BBR30:XREF3 is not updated correctly with Boletofrom bank
1005924 RFFOBR_A-The DME file does not include Rebate for ITAU (pre req for 1287633)
1287633 RFFOBR_A: Discount amount not calculated correctly
1234054 NF-e: function J_1B_NFE_MS_REQUESTS_DATA is not RFC enabled
1297534 NFe cancellation problems in GRC
1243964 NF-e: Adaption of xNFe interface of function NFE/NFE_SKIP
1165746 NF-e: Cancel - Error log not updated
1327465 The program /xnfe/update_erp_status is not updating R/3
1326691 BAdI for controlling the RFC call of external systems
1333136 Prevent simultaneous click on buttons in NF-e monitor
1333742 NF-e got the status 218
1354192 Validation rules: correction for fields TPLACA and T_UF1
1373175 Lock object for /XNFE/NFE_CREATE to prevent double transm
1376500 BAPIRET2 to provide the detailed information to ERP
1267455 Not possible to create different DOCREF per item using BAPI (pre req for 1373321)
1373321 BAPI_J_1B_NF_CREATEFROMDATA: DOCREF from Header go to item
1328583 NF-Writer posting of NF/NFe when mandatory fields not filled
1338166 NF-e: Random number and check digit lost after note 1328583
1259918 NF-e: RFC calls for request for cancellation or skip
1152140 NF-e: backend allows inconsistent new SCS (pre-req for 1298283)
1162852 NF-e: Inbound errors missed in error log of Monitor Report (pre-req for 1298283)
1163056 NF-e: Problems with printing via BADI method CALL_RSNAST00 (pre-req for 1298283)
1276438 NF-e: Parallel Phase not identified in messaging system (pre-req for 1298283)
1296515 NF-e: J1BNFE reset rejected NF-e after skipping request (pre-req for 1298283)
1297823 NF-e: Cancelled NF-e shows wrong action indicator (pre-req for 1298283)
1298283 NF-e: Skip for NF-e with validation error
1362969 NF-e: check cancellation for billing documents
1368159 NF-e: cancellation of invoices via original application only
1370933 NF-e: Accept Rejection to Cancel - wrong status in monitor
1376324 NF-e: Skip for NF-e with validation error
1140579 NFe: Field length conflicts from backend interface to XML
1357713 NF-e: Cancel of incoming NF-es does not update active table.
1173018 NF-e: Field control for Random Number and Check Digit (pre-req for 1366320)
1321517 NF-e: MIRO Credit Memos for NF-e shows error 8B 020 (pre-req for 1366320)
1366320 NF-e MIRO:Save is allowed without mandatory fields filled for NFe
1375066 NF-e: J_1BNFECHECKNUMBERRANGES ends too early, wrong subrc
1375894 NF-e: J1BNFE authority check for company code
1377879 NF-e: Report J_BNFECALLRFC aborts with message A098
1379062 NF-e: posting GR after cancellation leads to wrong NF-e
1357777 Cancel billing document without Nota Fiscal cancellation
1380861 NF-e Resend(proc.stat.07) with Signature error impossible
1362025 Error while sending Bacen Code EX with 0 on begining
1249819 NF-e: Field MODFRETE filled incorrectlyBom dia Marc de Ruijter,
Não dá para ler sua thread, mas imagino que seu validador esteja desligado.
No GRC vá em SPRO --> SAP GRC Nota Fiscal Electronica --> Configure System Response for Each Tax Number (CNPJ)
Para ligar/desligar o Validador basta clicar no check box na coluna Validation.
Observação: Para correto funcionamento do GRC deve-se sempre utilizar o validador ligado.
Após isto refaça seu teste, é provável que você receba um erro de validação para a NF-e. Veja em GRC Web monitor -> NFe Detailed View -> Validation History.
Atenciosamente,
Fernando Da Ró -
Replicar erro na Falha de Schema do XML para o ECC
Boa tarde pessoal,
estamos fazendo a migração para a versão 3.10 do XML e me deparei com uma situação que antes não acontecia com a versão 2.0.
Ao emitir uma NF-e e havendo erro em alguma informação o SEFAZ retorna erro 225 porem somente é possivel visualizar no monitor do GRC qual informação está incorreta onde na versao anterior o erro era replicado para o ECC.
Agora a pergunta; isso está correto onde a partir de agora somente será possivel visualizar no monitor GRC ou alguem tambem se deparou com esse problema e encontrou alguma nota?
Obrigado.Bom dia Carlos,
Em sendo a Sefaz GO a inconstância não me surpreende, mas a de se estar atualizado, principalmente com o removedor de caracteres e validador ativo para evitar a chance do programa da Sefaz se confundir que é o que parece estar acontecendo... Está apontando o problema num lugar onde a mensagem apresentada está ok.
Sugiro atualizar o sistema ao SP18 que é o necessário para trabalhar de forma saudável com layout 2.0
Atenciosamente, Fernando Da Rö -
Campo cNF do XML v.200 da NFe com 9 dígitos
Olá!
Estamos testando a NFe na versão 2.00 do XML.
Encontramos inconsistência no campo cNF do XML gerado pelo SAP.
Segundo o Manual do Contribuinte 4.01, o campo cNF deve ter o tamanho de 8 dígitos.
Nosso ambiente de testes está com o SP18 atualizado e o local de negócio atualizado para gerar o lay-out do XNL da NFe no na versão 2.00. Neste ambiente, o SAP está gerando o campo CNF no XML com o tamanho de 9 dígitos, sendo invalidado pelo SEFAZ.
O XML na RFC do SAP do cabeçalho da NFe, gera o campo
Somente para a versão 1.10 do XML da NFe que o campo cNF tem 9 dígitos, sendo que o primeiro refere-se ao tipo de emissão. Entretanto, para a versão 2.0 do XML, segundo o manual do contribuinte 4.01, dever ter 8 dígitos.
Não temos o GRC. Nosso serviço de mensageria é da Alliance.
Aplicamos as Notas SAP abaixo, porem sem sucesso:
Note 1519167 - Nf-e: Issuing type filled for XML-version < 2.00
Note 1520408 - Nf-e: Issuing type filled for XML-version < 2.00 and RFC = 3
Alguem já passou ou está passando por isso? Como está resolvendo?
Obrigado.
Abrçs
Heron CaetanoOla, respondendo a sua pergunta.
O formato com 9 digitos para a troca de dados entre o ECC e o GRC aparentemente foi mantida para compatibilidade das versões, porem, a validacao dos dados do NFEid por exemplo e os demais processos, para o formato 006 ( XML 2.0 ) leva em conto o novo formato de 8 digitos como demonstrado abaixo.
IF lv_id(2) NE is_nfe_header-cuf "Region
OR lv_id+02(02) NE is_nfe_header-demi+2(2) "Year
OR lv_id+04(02) NE is_nfe_header-demi+4(2) "Month
OR lv_id+06(14) NE is_nfe_header-c_cnpj "CNPJ of issuer
OR lv_id+20(02) NE is_nfe_header-mod "model
OR lv_id+22(03) NE lv_serie "serie
OR lv_id+25(09) NE is_nfe_header-nnf "NFe number
OR ( lv_id+34(01) NE is_nfe_header-tpemis "Issuing type
AND is_nfe_header-version NE gc_xmlvers1_erp ) "only for newer version then 1.10 (005a)
OR lv_id+35(08) NE is_nfe_header-cnf+1 "random number (except first digit fixed zero)
OR lv_id+43(01) NE is_nfe_header-cdv. "control digit
De uma verificada no seu ambiente do GRC, ele está com o SP15 instalado com todas as notas aplicadas ? inclusive no seu ECC, todas as notas referentes ao XML 2.0 foram realizadas com sucesso? -
How to add a calculated field in a list definition (schema.xml)?
Hello,
I'm currently trying to add a calculated field to a list definition (schema.xml).
I have put the following code at the end of the schema.xml for the list I want to create. But when I deploy and activate the feature for the list, it doesn't appear in the list field.
<Field ID="{EE20EC4B-4216-4259-A84F-C478CE42B70F}" Name="EC_EventsMgmt_CalculatedTime" StaticName="EC_EventsMgmt_CalculatedTime" Group="EC_EventsMgmt" Type="Calculated" DisplayName="Calculated Time" Required="TRUE" Hidden="FALSE" ReadOnly="FALSE" Format="DateTime"> <Formula>=DATE(2009,1,1)+TIME(EC_EventsMgmt_ScheduleHour,EC_EventsMgmt_ScheduleMinute,0)</Formula> <FieldRefs> <FieldRef Name="EC_EventsMgmt_ScheduleHour"/> <FieldRef Name="EC_EventsMgmt_ScheduleMinute"/> </FieldRefs> </Field>
Could you please give me some help and explain me why it is not working?
Thanks a lot.Hi there.
If I understand correctly, you create this list within the same feature?
If so, the list isn't available during the propagation, and therefore the calculated field can't be added.
If this is the case, then you could work around this by adding a feature activated event handler to your feature and add the calculated field programmatically in that event.
Hope this helps.
Regards,
Magnus
My blog: InsomniacGeek.com -
Envio de e-mail B2B via Abap - erro na visualização do XML
Boa tarde,
Em virtude da minha versão (GRC 10.0 e NW 7.11), apenas poderia implementar a solução de B2B dinâmico, caso utilizasse Java Mapping. Como meu conhecimento em Java é pequeno, optei por enviar o e-mail a partir do Abap do GRC.
O XML que estou gerando está com erro na tag <ns1:Transforms>. As tags acima desta estão ok.
Comparei com o XML original e os códigos-fontes são EXATAMENTE iguais.
O erro é "Página XML não pode ser exibida". Na instrução, aparece a seguinte informação: "Não é possível exibir a entrada XML usando a folha de estilos XSL".
Alguém pode me ajudar?
Se julgarem que, apesar de meu processo ser de NFe, preciso abrir a thread em outro tópico, basta avisar.
Obrigado.
Abraços,
Flavio.
Edited by: fgalmeida on Oct 6, 2011 7:09 PMResolvido.
Olhando o fonte do XML, verifiquei que ao final do arquivo haviam espaços em branco.
A solução foi passar o tamanho do xstring no parâmetro i_attachment_size do método add_attachment da função cl_document_bcs, conforme abaixo:
DATA lv_size TYPE so_obj_len.
lv_size = xstrlen( lv_content_xml ) .
CALL METHOD document->add_attachment
EXPORTING
i_attachment_size = lv_size
i_attachment_type = 'xml'
i_attachment_subject = 'XML NFe'
i_att_content_hex = lt_content_hex.
Obrigado.
Flavio. -
Xformbuilder error ... Could not save document Name/Name-Schema.xml
Hello everyone,
We're using 7.00 SP14 and I have a problem with the xml forms builder on one of our systems. We're having a 3 system landscape - all three are on the same patch level etc.
I was able to create a new xml form on one machine, unfortunately it doesn't work on our P-system. I tried to create a new form as well as copied an existing one - with the same error result.
While saving a project the following errors appear:
The following error occured when saving the schema: Could not save document Name/Name-Schema.xml. Reason: Operation is not supported
The project could not be saved on the server. Do you want to save a local copy?
Oct 13, 2008 2:45:43 PM - (ERROR)com.sapportals.wcm.app.xfbuilder.server.ServerManager :Could not serialize document: Operation not supported
Does anyone know what the problem is? I'd appreciate your help, thanks.
Sincerely,
Susanne
Okay I just found out that it's not possible to create a new folder in KM under xmlforms. That's working on the other 2 systems quite well. I have all the admin roles but somehow somewhere somewho must have restricted that. We found out that ice, etc, runtim, entry points and maybe even a few more aren't setup to create new folders in there. Does anyone know where/how to change that? It doesn't work with Details - permissions etc.
Edited by: Susanne Zahn on Oct 13, 2008 3:40 PMFor anyone who's interested in the solution.. there you go.
14.10.2008 - 17:53:00 CET - Antwort von SAP
Dear customer,
Can you please check whether the repository /etc is in read-only
mode?
Please navigate to -
System Administration -> System Configuration -> Knowledge Management
-> Content Management -> Repository Managers -> File System Repository
There you can see the checkbox for "read-only".
Please insure that this is not ticked. If it is, please uncheck it
and building/saving the project again. -
I am implementing a custom schema.xml for a list template. These is a field that will be provisioned separately in a different feature. However, I would like to reuse that field in schema.xml. Can I do that? Can I refer to its GUID as follows in Fields
section?
<Fields>
<Field ID="{35788ED2-8569-48DC-B6DE-BA72A4F87B7A}" Name="Custom_x0020_Order" Type="Number"></Field>
</Fields>
ThanksHi,
it's long ago for me, but if you add a feature activation Dependency to the feature, containing the List and targeting the field containing feature, you should do fine.
Such dependencies are defined in Visual Studio and result in a node under "ActivationDependencies" int the Feature-Definition:
<Feature xmlns="http://schemas.microsoft.com/sharepoint/" Title="List Containing Feature Title" Creator="not necessary" DefaultResourceFile="Relevant for localized output" Description="..." Id="cf718ba0-6ee9-4170-a098-32df08c62d08" ImageUrl="if necessary" Scope="Web">
<ActivationDependencies>
<ActivationDependency FeatureId="GUID OF THE FEATURE (IMPORTANT)" FeatureTitle="Feature Title" />
</ActivationDependencies>
<!-- and so on -->
If you now try to activate your list containing feature without having you field containing feature activated before, SharePoint will hint you towards the missing feature instead of activating you list feature.
Best regards!
Peter -
Hey,
I have to write with a custom list definition. The list definition must also include a
content type.
But the problem is I cannot reference the content type by guid. The list definition must
run in different site collection and the content type was build manually. The only constant is the content type name.
How can I reference the content type by name in the list schema.xml?
Thanks for your help
Regards
StefanHi,
According to your description, my understanding is that you want to reference the content type in a custom list definition.
I have something to confirm. Did the content type is located at the different site collection from the list ?
If yes, you need to use content type hub to publish the content type to the other site collection firstly and then reference it in the schema.
If No, then in the list schema, if you need to reference the content type, you need to know the content type ID firstly, it is necessary in the schema.
You can use the PowerShell command to get the all content type details like the command below:
$site = Get-SPSite http://yoursiteurl
$web = $site.RootWeb
ForEach($ctype in $web.ContentTypes){write-host $ctype.Name": "$ctype.ID}
More information:
How to: Add a Content Type to a SharePoint List
Publish a content type from a content publishing hub
Understanding Content Type Hub (CTH) in SharePoint 2013
Thanks
Best Regards
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] -
"Person or Group" Field in List instance (Schema.xml)
hi all,
I created new List instance and I added new Field Employee to the list instance. The Employee field in the Schema.xml is like:
<Field Name="Person" ID="{f3c1416f-69dd-4172-b05f-5df45c86ee56}" DisplayName="Person" Type="UserMulti" Mult="TRUE" /></Fields>
and this work fine.
But I cant see the EntityEditor like below pic:
they are disapear.
Can anyone maybe help me?
P.S. I created one column via UI on the same list and in the SharePoint Manager 2013.
Its the same I dont see the EntityEditor and here is the Schema.xml for the test column:
<Field Type="UserMulti" DisplayName="test444" List="UserInfo" Required="FALSE" EnforceUniqueValues="FALSE" ShowField="ImnName" UserSelectionMode="PeopleAndGroups" UserSelectionScope="0"
Mult="TRUE" Sortable="FALSE" ID="{aefd55b0-3d3e-44ba-a649-82391061ca38}" SourceID="{93681c67-ca5f-4598-a412-3efee82a18d6}" StaticName="test444" Name="test444" ColName="int3" RowOrdinal="0"
/>
thank you in advance
BR
AhmadHallo Mr. Sabir,
sorry I was sick and I couldn't answer you before :-(.
I use SP 2013 (and not SP 2010, maybe I must Active a feature!) and in my Schema.xml I have exacly the Schema:
<Field Name="Person"
ID="{f3c1416f-69dd-4172-b05f-5df45c86ee56}"
DisplayName="Person"
Type="User"
Required="FALSE"
ShowField="ImnName"
UserSelectionMode="1"
UserSelectionScope="0"
Group="Custom Columns"
StaticName="MyUserColumn"
/>
srv206/Lists/CustomList/NewForm.aspx
when I open the above URL I get like below picture:
if you or other one here have/has an advice or other idea thanks in advance
BR
Ahmad
SP 2013 & SPD 2013 & VS 2013 & MSSQL 2012 -
Hi,
I have created a blog site with the available site template few days back. Now we have the requirement of having the attachments in the body of the comments section.
So, I updated the schema.xml of the comments list available under ../templates/blog/lists/comments/schema.xml to have rich text for the Body field.
With this change, I created a new site and it was working fine. Change is reflected in the new blog site.
However, this particular change is not reflected in the existing blog site. Any changes made to the schema.xml is not effecting the old blog site.
Can anyone suggest what can be done for the change to be reflected in the old blog site?
Thanks in Advance,
Regards, Keerthi SuryadevaraHi,
According to your post, my understanding is that you wanted to add attachments in the body of the comments section.
You can add the the Code inside the Default list pages. For more information, you can refer to:
Enable Attachment in SharePoint Blog post list and display the list Attachments
In addition, you can add an enhanced rich text field to the comment list and remove the body field. Then you can insert files into comments, too.
Here is a similar thread for your reference:
http://sharepoint.stackexchange.com/questions/77194/how-to-add-attachments-for-comments-list-in-sharepoint-blog-2010
Best Regards,
Linda Li
Linda Li
TechNet Community Support -
Update list definition schema.xml after deployment
I was wondering if anyone here has any experience with updating the schema.xml file after deployment. I have a solution that I will outline in this post, but I feel like it is a delicately balanced hack instead of a real solution. Any Information
that you can provide is greatly appreciated!
To begin, I am trying to create a new taxonomy site column, use this new site column in place of an old one in an existing content type, and update the list definition (and all existing lists) to show the new site column instead of the old.
The content type was originally deployed via an elements.xml file. From what I understand, once deployed this file should never be modified. So, via code I define my new site column, add the site column to the content type, and delete the old
site column from the content type. I perform an update(true) on the content type so that the change is pushed to all list instances. At this point, I can go to any list and the new/edit form for each of those lists does not show the old site column
but does show the new. So far so good!
There are two problems at this point. If I try to create a new list from the definition, I get a list that contains the site column that I deleted AND the new site column. Also, the deleted site column name still appears in the default view.
I tried removing the old and adding my new site column to the schema.xml, but this breaks all existing lists that were made from this schema.xml (specifically, it is a taxonomy field and none of the taxonomy fields work after updating). I can create
a new list from the list definition that works fine, but I still need existing lists to work.
The solution that I ended up on was JUST removing the no-longer-necessary field from the schema.xml, and then adding my new field to the ViewFields list in the schema.xml. If I do this, everything is happy even though the only mention of the new field
in the schema.xml is in the ViewFields section.
So, with all of that said... does this make sense? Am I doing this the correct way, or does this just work for now... and it will blow up later?
Thanks in advance!I am sorry if I have caused confusion. I am not doing what you think that I am doing :)
All of my issues that I reference above are encountered when I deploy via WSP/Powershell. I am not changing any files directly in SharePoint. When I mentioned changing the elements.xml and schema.xml files above, I am talking about in Visual
Studio prior to packaging everything in WSP and redeploying. I will re-word my previous post to better emphasize my questions:
Isn't changing the elements.xml via Visual Studio and deploying the same as changing it directly? I have tried numerous times to change a content type elements.xml
file in Visual Studio, Deactivate/Retract/Remove/Install/Deploy/Activate the new version via WSP,
and then perform a content type update(true) in the feature activated
to push the changes to all child content types... and it doesn't change the lists version of the content type. This is why I thought that guidance of "don't change the definition file" applied to elements.xml altogether after deploying.
Either way, my code approach for getting these fields updated is working, so I can probably just proceed with that approach.
This is where it gets very strange. I see everyone indicate that a schema.xmlchange does not affect existing lists that were made from a list definition
when updating the package in Visual Studio, Deactivating/Retracting/Removing/Installing/Deploying/Activating the new version via WSP. I am 100% seeing the opposite of this. When I update the schema.xml file
in Visual Studio and then deploy via WSP/Powershell, my views (in existing lists) change to match the new schema.xml as soon as I deploy the changes. I don't know if this is working differently in 2013 than it did before.
Hopefully this better indicates the situation. My apologies!
Thanks again!
Hi,
Do you have a solution for case 2)?
I just confirmed for case 2), you are right. This happened for both SP2010 and SP2013.
I've tried to add more column in the schema.xml, then re-deploy solution. After that, all existed lists are effected the new schema.xml. However, by the work as design of SharePoint OOTB, it could not be effected because after creating a list, all schema.xml
is copied to database and it will work on the separate space. It's so strange.
if you have a solution to fix or found out something else, please share it.
Thanks
/hai
Visit my blog: My Blog | Visit my forum:
SharePoint Community for Vietnamese |
Bamboo Solution Corporation -
Hi, In Sharepoint 2013 i have Rename the Field of the Task List using visual studio Schema.xml file
can u tell me anyone ?It is not recommended to update 14 Hive List Schema.xml instead you can create custom list definition and deploy in SharePoint environment :
Please make reference of XML file from task list to create custom task list in VS project as your requirements.
Refer the below msdn article which will same for SharePoint 2013 as well:
Create Custom List Definitions in SharePoint 2010
If my contribution helps you, please click Mark As Answer on that post and
Vote as Helpful
Thanks, ShankarSingh(MCP) -
NFe 3.10 - Erro 225: Rejeição: Falha no shcema XML da NFe
Boa tarde.
Estamos com problema no Schema do XML, já verificamos as informações do post abaixo:
http://scn.sap.com/thread/3714800
Aqui também ocorre o mesmo problema e quando reenviamos a nota o xml é processado. Porém, precisamos encontrar uma solução
onde não seja necessário o reenvio manual do documento.
Baixamos o XML com problema e depois da validação no SEFAZ (após o reenvio) e a unica diferença é a tag abaixo:
Ela é criada após a validação do XML?
*** XML Erro Schema
<?xml version="1.0" encoding="utf-8" ?>
- <NFe xmlns="http://www.portalfiscal.inf.br/nfe">
*** XML OK, após o reenvio da NF
<?xml version="1.0" encoding="utf-8" ?>
- <nfeProc xmlns="http://www.portalfiscal.inf.br/nfe" versao="3.10">
- <NFe xmlns="http://www.portalfiscal.inf.br/nfe">
Gostaria de saber se alguém já passou por este problema e qual foi a solução aplicada.
obrigado
Juliano DinizOi Michael,
Essa declaração que o José comentou é diferente mesmo, não vi em nenhum outro cliente e ela que deu erro no validador da SEFAZ no seu teste. Se você remove essa TAG e faz o teste no validador da SEFAZ RS o XML aponta outros erros.
Teoricamente o XML começaria assim:
<?xml version="1.0" encoding="UTF-8"?>
<NFe xmlns="http://www.portalfiscal.inf.br/nfe">
Além disso o XML do TXT tem umas quebras de linha que separaram o conteúdo das TAG's e causaram erro no validador da SEFAZ tb.
O validador do GRC é basicamente uma função que aponta erros técnicos no preenchimento dos dados que vieram do ERP ( campos obrigatórios em branco, campos numéricos com valor alfanumérico, etc...) porém ele não validaria a estrutura final do XML ( encoding, montagem das TAG's e namespaces adicionados ).
OBS: No arquivo adicionado tem o XML completo e por uma questão de "data protection" eu não recomendaria disponibilizar esse tipo de arquivo na internet, pois ele contém dados teoricamente sigilosos de negócio ( Clientes, transportadores, produtos/preços, Certificado digital da empresa emissora, etc...).
att,
Renan Correa -
PLEASE : JAVA PARSER SCHEMA XML doesn't work
Hi,
I search how can I parse a xml document with schema, which works with Sun'SAX in JAVA.
I have no real idea to it, but I think that JAXP can work (is it a good idea?)
I have found this exemple :
http://dataml.net/articles/ValidateXMLSchema/part1.htm
This example is often posted in the forum, but for me it doesn't work, and you? have you had a probleme with it?
Have you others examples which work or tutorials for parse xml with schema with SAX in java?
Furthermore what are the specifics recommandations to install JAXP ?
Thanks a lots.Nobody can help me?
please
Maybe you are looking for
-
How can I link iTunes Match to my proper Apple ID? I have two ID's and my phone accesses iCloud with the proper ID but it insists on trying to access iTunes Match using the wrong ID so I get the message that I'm not registered for iTunes Match.
-
Where can i purchase a Nomad Jukebox Zen 6
Does anybody know where i can purchase a Nomad Jukebox Zen 60GB? I have tried **bleep** Smith, Tandy, JB HiFi, Retravision, all in the Ringwood area. Also tried JB HiFi in Knox and **bleep** Smith Powerhouse. The issue was not a lack of stock, but on
-
HT5794 How do I get .lso-files, made back in the day, to open in Logic Pro
My old Logic Express 8 won't open them, I need Logic Pro 7.2.1 it tells me, . It's like that program never caught on in my network, nobody has it. All help greatly appreciated, a DMG-file , on DVD.....or maybe even you converting them for me on your
-
Error assigning value to page item
I create a "SQL Query (Pl/Sql Function Body Returning Sql Query)" region, and also an item on the page called :P1_TEST. In the Region Source for the region, I have the following codes: declare l_sql varchar2(32676); BEGIN :P1_TEST := 0; l_sql := 'sel
-
Rear glass cover has cracked without being dropped twice in four months
I have had my z3 since December the notification bar stopped working after two weeks, after a month the front and rear screens cracked in my pocket I have paid £130 to have this repaired (outside of warranty) so I paid £50 to have the front and rear